Solution Components Creation Guidance Needed

[SueA]

Hi:

I have an existing Solution that has a Canvas App, Eight Power Automates and two Connection References (SharePoint and OUTLOOK). I have few SharePoint lists as my data source.

I need to copy the Canvas App and tweak Power Automates a bit with Notifications verbiage and use exactly as-is all the components for another project.

What is the best way to do this?

If I create a New solution and then add components with "Add existing" option on the top menu bar, I am told that this way there could be an issue when I migrate from DEV to UAT or PROD. The best way is to create the components within the solution. But, that means for me to reinvent the wheel and spend all that time again...

Is there a way to save as the entire solution?

If not, is there a better way to handle duplication of the Solution components process?

Please advise.

Thanks,
SueA.

[Amik · Accepted solution]

@SueA , at present, there is not an option to copy a Solution or "Save As" an entire Solution.

A simple option is to ensure your Canvas App and Power Automate Flows are treated as completely separate entities from the original Canvas App and Power Automate Flows.

Create a copy of your Canvas App (via Save As in the Canvas App design studio) and create copies your Power Automate Flows (via Save As in the Flows page). Create a new Solution and import those components into that Solution.

You do not need to include the Connection References. A Connection Reference exists and is provisioned only once in the target environment, irrespective of which Solution those connection references reside.

For example if Solution A contains SharePoint and OutLook connection references, and you then import Solution B, which also contains Power Automate Flows which depend on SharePoint and Outlook connectors, that Solution will use the same Connection References as Solutions A.

[SueA]

Hi, @Amik 

When you mention, import those components into the solution:

The only option I see within my NEW solution is "Add existing" to bring in (import) the items I have created using "Save As" option in the existing solution. Is this the only way? If so, do I bring in the components that way in hopes that it will not create any migration issue in the future?

Thoughts?

Thank you,

SueA.

[Amik]

Hi @SueA - "import" was a poor choice of words on my part. By import I simply mean add those components you created into the New Solution (yes, via Add Existing).

You are simply creating a new solution, and adding the components you created into that Solution.  

Migration issues can occur if you include any specific components that the other Solution is dependant on. A typical example is a Table or a Power Automate Flow. In your case, there is no concern because you have created separate/stand alone components unrelated to the other Solution.