-
Add "Not ready to Invoice" on Billing status option set on Actuals
I have a suggestion to improve the Billing status field on Actuals. Instead of having "N/A" as the status for "Not ready to invoice", could the team add an option with a text "Not ready to Invoice" to the option set? This would make it easier to use the field: 1. Not having a "Not ready to invoice" option is confusing to the user. They want to see the text in there. 2. We are unable to mass edit records and change their value from "Ready to invoice" to N/A. Setting an option set to N/A is not picked up in mass edit. 3. Having "N/A" means the field has to be accessed as "does not contain data" in Flow. This isn't immediately clear to everyone as Flow is still missing that option in conditions. -
Allow to set Actuals to "Ready/Not ready to Invoice" from Order and Project entities
Being able to set Actuals to "Ready/Not Ready to Invoice" on Order and Project (from related records) will streamline invoicing greatly and will also be a big boost to user experience. At the moment we are getting constant feedback that users do not want to perform this functionality from Actuals. They work from the context of Orders and/or Projects and want to interact with Actuals from within those entities. -
Enable "Correct this invoice" for Product-based Lines
Please extend the "Correct this invoice" functionality to cover scenarios where an Invoice has been confirmed and Product-based Lines have to be corrected. -
Display more rows and information on custom Insight Cards
Custom Insight Cards are a really power way to deliver information, however the area for custom data is quite limited. My suggestion is that custom Insight Cards would display more than 3 rows of data and that the visible area would automatically expand when there is more than 3 rows of data.
-
Include custom Insight Cards in Customer Engagement Plan and Application Enterprise licenses
Custom Insight Cards are a very powerful feature and the core CE applications, Sales, Customer Service, Field Service and PSA benefit hugely from this feature. My suggestion is to include custom Insight Cards in Customer Engagement Plan and Application Enterprise licenses.
-
Custom Insight Cards should be visible under AI setup despite how the related Flows are created
Currently custom Insight Cards are only visible under AI setup when the cards are created from the context of an environment's AI setup. Custom Insight Cards created by creating Flows from the context of an existing solution or from flow.microsoft.com should also be visible under AI setup. At a minimum, there should at least be links to Flows that have actions for Insight Cards.
-
Allow us to choose a target solution for custom Insight Card Flows created from AI setup
Currently all Flows created from AI setup end up in the related environment's default solution. Please allow us to choose a target solution when creating a Flow for a Custom Insight Card from AI setup.
-
Open up Resource Assignments for contour changes on Project entity's Resource Assignments tab
At the moment changes to RA contours are locked due to Project for the web. Changes to RA contours are mission critical so that project managers are able to align bookings (Bookable Resource Bookings) and task assignments (Resource Assignments). When RA contour changes are locked, there is nearly always a discrepancy in RAs and BRBs, when looking at a Project Team Member and a PTM's bookings vs. assignments. -
ProjOps needs its own Business Process Flow for Opportunity
Right now, ProjOps shares the OOTB Opportunity Sales Process BPF with core Sales: Installing ProjOps on top of core Sales overwrites the OSP BPF with a ProjOps specific process ribbon. While customizing OOTB BPFs is not best practice, many organizations have done so and when they install ProjOps after core Sales, their BPF is overridden. Please add a separate ProjOps specific BPF for Opportunities. This way project bases sales scenarios can be run with a dedicated BPF on Opportunity. -
Enable project templates
Project templates is one of the most frequent requirements in PSA+ProjOps implementation projects. Templates drastically reduce the time required to set up complex project plans. Please bring back project templates as we know them from PSA.