This article is part of the Working with Power Automate Solutions series and of the larger Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.
As mentioned in the article where I introduced solutions, when you have a solution which is ready for deployment, or even where you have made changes to the solution since it was last published, then the solution should be published for the implementation of Application Lifecycle Management (ALM) .
While technically speaking, a solution which does not use the Common Data Service (CDS) does not need to be published, I’d generally recommend following best practice of publishing all solutions.
For the work I have been doing with Power Automate, involving Business Central and approvals, I am interacting with the CDS as the approvals store the history and status of pending approvals in CDS.
To publish a solution, open the solution and click the Publish all customizations button at the top of the solution page:
Once the publication is complete, a green status confirmation bar will be displayed towards the top of the screen:
With the solution published, it can now be exported (although I should not that the export process itself does prompt for the solution to be published, so you could publish from there instead of using this method).
Over the next few articles, I’ll take a look at exporting and import the solution as both an unmanaged and managed solution.