Power Community

Power Community

What’s next for Dynamics 365 Project Service Automation and the project management and accounting (PMA) capabilities within Dynamics 365 Finance?

By, Gurkan Salk, Principal Group Program Manager

On February 19, 2020, we announced  —a new application that will bring together capabilities from Project Service Automation, Microsoft Project for the web, and project management and accounting within Finance into a single offering. Microsoft Dynamics 365 Project Operations connects cross-functional teams within a single application to win more deals, accelerate delivery, empower employees, and maximize profitability.

Microsoft will continue investing in a solution in the professional services automation market with Dynamics 365 Project Operations becoming available for public preview in June 2020 and generally available on October 1, 2020. 

Bringing together our existing Project Service Automation, capabilities from Microsoft Project for the web, and project management and accounting from within Dynamics 365 Finance is key to our vision.  Microsoft Project will continue offer project management (PM) and project portfolio management (PPM) solutions for PMO leaders. With the introduction of Dynamics 365 Project Operations, we will now include project management capabilities directly in the flow of work for our customers looking to streamline project-based service operations.

As part of this announcement, we will be grandfathering our current customers that are using Dynamics 365 Project Service Automation and/or the project management and accounting (PMA) capabilities within Dynamics 365 Finance into this new offering.

We look forward to continuing to work with our customers as they adopt Dynamics 365 Project Operations, as well as the champions and advocates who have supported us along the way. 

Here are some important details to help our customers with the transition:

  1. What should my organization know about this transition?

Customers evaluating our in-market solutions today should feel comfortable to continue their evaluation, purchase, and installation of our product, with knowledge of a rich and full product roadmap through our vision for Dynamics 365 Project Operations.

Current customers will get access to migration tools and will be grandfathered into Project Operations licensing. Please refer to the impact overview below:

Eligible customers are defined as either 1) current customers who have purchased or renewed Dynamics 365 Project Service Automation, Dynamics 365 Unified Operations plan, or Dynamics 365 Plan 2 prior to October 1, 2020 or 2) current customers who have opted in via the defined process below. Customers who are not eligible by October 1, 2020 will be unable to access Project Service Automation or project management and accounting (PMA) capabilities after October 1, 2024.

Opt-in process:

To allow time to opt-in, Dynamics 365 customers that are entitled to but are not currently using Dynamics 365 Project Service Automation or PMA capabilities within Finance will have until December 31, 2020 to notify Microsoft that they intend to implement these products or capabilities. You can opt-in at any point between May 1, 2020 and December 31, 2020. If you are not currently using these products, but are entitled to them and want to opt-in to ensure service availability, submit a support ticket here.

  1. Will Dynamics 365 Project Service Automation and project management and accounting (PMA) capabilities be supported? Will there be additional feature development?

Microsoft will provide support for our Dynamics 365 Project Service Automation offering until October 1, 2024. We will not be adding new capabilities into Dynamics 365 Project Service Automation. Going forward, the re-envisioned Dynamics 365 Project Operations product based on existing Dynamics 365 Project Service Automation and Dynamics 365 Finance PMA capabilities will be enhanced and maintained as part of this new offering. Our Dynamics products updates webpages will continue to be updated to reflect our future investments.

  1. Can I export my organization’s data, and will there be migration tooling available?

Yes, Microsoft will provide update scripts for Dynamics 365 Project Service Automation and data migration tooling for current customers using the project management and accounting capabilities within Dynamics 365 Finance. Using these, current customers will be able to upgrade/migrate at their pace. You will receive more information about upgrade/migration tool availability from within the Dynamics 365 Project Service Automation and Dynamics 365 Finance products as we get closer to the GA date of Dynamics 365 Project Operations of October 1, 2020.

  1. Will I have to keep paying for Dynamics 365 Project Service Automation?

Yes, as current customers can continue using these products and capabilities over the next two to four years, depending on contract type, all contracts will remain in place until renewal or expiration.

  1. Where can I learn more about other ISVs that provide Dynamics 365-based solutions for the professional services market?

Find the right apps for your business and solutions tailored to your industry on Microsoft AppSource.

  1. Which capabilities that are currently part of Dynamics 365 Finance will be part of Dynamics 365 Project Operations?

Existing PMA capabilities within Dynamics 365 Finance that will be part of Dynamics 365 Project Operations include all project management and accounting capabilities, as well as expense management.

  1. Will this impact my Microsoft Project licenses?

The introduction of Dynamics 365 Project Operations does not impact your Microsoft Project licenses.  Microsoft will continue to offer project management and project portfolio management solutions to our customers.

  1. What are my next steps?

You can continue business as usual without any immediate disruption. We recommend you reach out to your Microsoft account team or partner to get more information and build a plan to transition from the Project Service Automation service by October 1, 2024, or your contract end date, whichever comes first.

Learn more about Microsoft Dynamics 365 Project Operations.

- Advertisement -spot_img

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisement -spot_img
- Advertisement - Advertisement

Latest News

Power Fx: Error handling graduates to preview

We are thrilled to announce that the long-time experimental feature Formula-level error handling has moved forward to preview. As a result, you and your end users will enjoy higher reliability and more transparency about what is happening in your apps. It’s a huge step. Adding error handling to an existing language turned out to be a very tall order, touching almost everything, from data types, to functions, to the runtime. Thank you for all of your support, feedback, and patience as we got this done. What does it mean for you? Your apps will more reliably detect and report errors.You can write blank/null values to a database.You can detect and replace errors with the IsError, IsErrorOrBlank, and IfError functions.You can control error reporting and logging at a central location with App.OnError.You can create and throw your own custom errors with the Error function. Error handling is a big change in behavior. By entering preview, we are signaling that we believe we are done, that we anticipate no further significant changes from here. Many of you already use error handling in production and this move to preview should only embolden more of you to do so. If significant changes are needed from here, we will treat them as a separate feature. We are rolling this out slowly as it is such a big change. All of you will soon see that the Formula-level error handling switch has moved from experimental to preview in the settings (as of version 3.22082). It will still be default to off for most tenants. Over the coming weeks we will slowly change the default for new apps only to on across the tenants. Makers can still disable this feature and will be able to do so for a long time. I say again: we are changing the default for new apps only. Existing apps will continue running as they always have. We have no plans at this time to turn this on for existing apps, and as this is such a big change, we may never do this and make this a permanently available switch. Your feedback will guide us. The documentation for Error, IfError, IsError, IsErrorOrBlank functions and the App.OnError property covers these changes. IfError and IsError are very similar to their Excel counterparts. We are also working on overview docs that will be released shortly. But before that, let’s take a brief tour. Let’s start with what Excel does, the inspiration for Power Fx. For an error like division by zero, Excel is very clear that something has gone wrong with a # error message that shows right in the cell. This error will propagate to other cell formulas if A1 is used in a formula: Today, without error handling, Power Apps won’t report anything in this scenario, instead treating the division by zero error as a blank value. That’s not good, as the maker and the end user of the app have no idea something may have gone wrong: Errors happen. Unexpected data flows in, networks go down, storage fills up, to name just a few situations that an app may encounter in the real world. Makers don’t often think through all the ways that things can go sideways which makes default error handling even more important. Returning a blank for an error is also a problem because blank is a legitimate value in our type system and in many databases. Without error handling, Power Apps won’t allow you to write a blank to a database instead thinking it is an error. So, instead of returning an easy to ignore or misinterpret blank value, with error handling turned on we now report an error to the end user (the error banner) and show the formula as having an error to the maker (the red filled in circle on the control): Further, if you look at the value of the formula, it is not a blank but an error value. Just as any formula can result in a blank, now any formula can also result in an error: Now, we still aren’t showing an error in the label control itself as Excel does. We couldn’t do this generically because, unlike Excel, the error could be on a property of a control for which there is no way to display the error. For example, where should an error on a slider control? Where should an error be shown for an imperative operation in the middle of a button’s OnSelect formula? We settled on showing the end user banner and flagging the control in the design experience. That’s not to say you can’t detect and display an error in that label control. Error handling provides a wealth of mechanisms to control how errors are handled and reported. For example in this case, we can wrap the division by zero with an IfError function to return a custom message in the label: The Text function call is required for type compatibility. Or we can use IfError to throw a different, more specific error with the Error function: Or we can have a catchall for all errors in the app with App.OnError. For example, we can log the error and present a different message to the end user: If we look at the log, we see the details of the captured error from FirstError (and there is also an AllErrors), including where it happened and when it was detected: The possibilities are endless! You now have all the tools you need to detect, replace, report, and log errors, including a good default behavior if you never take advantage of these tools. And, bonus, you can also now write blank (or null) values to databases. Please let us know what you think in the Power Apps community forum. There is a dedicated and active space for error handling discussions at Error Handling – Power Platform Community (microsoft.com).

More Articles Like This

- Advertisement -spot_img