-
Enable quote revisioning so that new versions of a quote can be created
Quote revisioning is a frequent requirement in a sales process. Users are looking for a simple way to revision their quotes, based on fine adjustments to project scopes. With revisioning, an organization's quote process has transparency and changes are documented as revisions. Revised quotes also keep activities seen on the timeline. -
Enable programmatic create, update, delete operations on Project Task and its related entities
Being able to programmatically CUD the Project Task entity is a frequently seen scenario in PSA+ProjOps projects. Many processes around project management require programmatic CUD operations to the PT entity and its related entities. Organizations have CR processes tied to new tasks, project template as well as programmatic project creation processes based on various different business scenarios. Power Automate nowadays further extends the typical requirements outside Power Platform to tools like Jira and inside the three clouds to tools like Azure DevOps and Planner so being able to CUD the Project Task entity is crucial. -
Dual Write alerts based errors should be more descriptive on CE side
Dual Write alerts essentially can pause DW maps and an error is displayed in CE, when an alert fires off. The errors in CE are not descriptive enough and are hard for basic users to understand. Please make errors in CE more descriptive, when they originate from DW alerts. This way users don't keep trying to save records in CE, if F&O is down and DW maps are paused. -
Introduce a CE only SKU for licensing
The value prop of ProjOps is heavily CE only oriented especially for smaller markets with few net new F&O implementations per year. While a hero story implementation can be seen as the holy grail of ProjOps implementations, a cash cow implementation will be a CE only scenario. ProjOps needs a proper base license for CE only scenarios and the current SKU is beyond a CE only scenario's realistic value prop. -
Allow recall of time entries / cancelation of approvals for entries with billing activity
Currently time entries / project approvals with billing activity can't be canceled / recalled. Please allow us to recall / cancel records with billing activity, when a time entry has gone through the entire invoice / correct invoice cycle. I.e the ask is to allow for a recall / cancelation of records that have an unbilled sales actual after having gone through the invoice / correction cycle. Use cases: 1. Invoice has been sent out to the wrong "bill to" customer and approvals for related time entries need to be canceled so that they can be reapproved for split billing to kick in. 2. Accidental approvals for time entries have occurred and related time entries need to be recalled after a invoice / correct invoice cycle. -
Include a Purchase Order reference column for Order and Invoice for integrated and Lite deployments
As a project manager, I want to add a Purchase Order reference number on an Order, so that my customer's financial department is able to match our invoice with their PO reference number. Technical: Column on Order to which a PO reference can be entered. The value is carried over to a created proforma invoice, when one is created. Dual Write will carry the value to a Project Invoice Proposal in F&O and upon posting the Project Invoice Proposal, the value is carried over to Project Invoice. Comments: While this is an easy scenario for Lite, the scenario is more complex in integrated due to several moving parts needing customization and maintenance in ALM: Dataverse tables with workflows, DW maps, F&O tables. A PO number reference is a common requirement so it would make sense to have this OOTB. As PO numbers may change mid-project, an alternative approach is to enter a PO number on a proforma invoice in Dataverse and have it carried over to F&O like in the aforementioned way. -
Leverage Actuals when migrating fully invoiced billing milestones at cutover
Currently, migrating fully invoiced billing milestones at cutover requires the creation of billing milestones and a confirmed proforma invoice. This is either a tedious manual process or requires very advanced knowledge of programmatically creating milestones and calling relevant actions to create and confirm invoices.
My suggestion is to leverage Actuals for creating Billed Sales milestones, which could then be factored in for RevRec. This would make this part of the cutover a lot faster and simpler, as the creation of Journals and Journal Lines can be done in bulk.
Migrate fully invoiced billing milestones at cutover | Microsoft Docs
-
Enable the Bookable Resource table for Dataverse search (set "Can enable sync to external search index" managed property to true)
Currently, the Bookable Resource table is not enabled for Dataverse search as the managed property "Can enable sync to external search index" is set to false.
My suggestion is to set that property to true and to enable the Bookable Resource table for Dataverse search.
Example use case:
I'm processing change request forms with AI Builder. The CR form has a project manager defined on it, and I want to search Dataverse for Bookable Resources that match the defined PM on the CR form.
This idea is related to SR 2112090050002378 and has work item 2228381 created for it. The idea has been created to increase visibility and to help with prioritization.
-
Establish guard-rails in task-based billing to prevent lost Unbilled Sales Actuals, when msdyn_includedtasks is se to "Selected project tasks only"
Currently, when msdyn_includedtasks on an Order Line is set to "Selected project tasks only", there's a big risk that time entries will not result in an Unbilled Sales Actual. This can happen if:
- Chargeable Tasks have not been set on an Order Line.
- Project Task lookup is null on a Time Entry.
My suggestion is two-fold:
- Present a user with a notification on the Order Line table when msdyn_includedtasks changes to "Selected project tasks only". This will ensure a higher probability of the user setting Chargeable Tasks.
- If msdyn_includedtasks is set to "Selected project tasks only", make msdyn_projecttask on the Time Entry table business required. This should be possible with JavaScript.