How to move the Document Automation Kit to an UNmanaged Solution?

[RichardUchytil]

I've used the AI Builder with the Document Automation Kit, made some modifications, and I now have a working application that I want to move into a testing environment and eventually to Production.  The problem is, when I got started by clicking the kit, it had the solution in a Managed solution.  I didn't know anything about Managed vs. Unmanaged solutions when I started.  From what I've read, in order to move all the pieces for this app from Dev to Test/Prod, I need to do it with Solutions, and the Dev solution needs to be UNmanaged.

I've created a new UNmanaged solution, but how do I get the pieces out of the Managed solution and into my UNmanaged solution?  I don't want to recreate everything from scratch.  Thanks!

[Antrod · Accepted solution]

Hi @RichardUchytil ,

From within your unmanaged solution you can click on Add existing and add all the components that are in the managed solution (but you need to do it manually for each component type). For example, here I added all the cloud flows in the solution:

[RichardUchytil]

I did that but in my unmanaged solution it's showing the flow as being managed.  Don't I want it to be unmanaged?  Same with the dataverse tables, they come in as managed.

[Antrod]

It's possible to add managed components in unmanaged solutions. Managed components can also be modified to some extent (depending on modification policy). In the case of the starter kit, you can modify the flows or apps for example. Modification of a managed components creates an unmanaged layer on top of your managed component (but you can't see this layer in the experience).

You should be able to export such solution and import it in a different environment. Let us know if that works.

[RichardUchytil]

I have been able to modify the starter kit flows and did notice it created an unmanaged layer on top.  I didn't realize I could put the managed items in an unmanaged solution to be able to move them to a new environment, I thought they had to be unmanaged.  I was able to save one of the managed flows to a different name then add that to my unmanaged solution and it came in as unmanaged.  Should I be doing that or just add the managed flow/items?

[Antrod]

I would say that it's better to keep initial names and see if your ALM process works fine (unless I'm missing something, it should work). In case you face an issue, then yes it could be a good idea to rename the components.

[RichardUchytil]

Gotcha.  My one concern is if someone else tries to use the starter kit they will get the same names and could override/modify my stuff without realizing what they are doing.  But I'll try first without renaming, and if that works, then with renaming.  Thanks very much for your help!

[RichardUchytil]

I was working with the managed flows in the unmanaged solution and decided to rename them since they stand on their own, nothing else is linked to the names. When I renamed them in my unmanaged solution, I noticed they got renamed in the managed solution. Oops! I didn't want that. I guess I need them to be unmanaged in my unmanaged solution if I want to rename them. Does that sound right?

[Antrod]

Indeed, if you rename them, they will be renamed everywhere as they are references and not copies. You could as well do copies and rename them.

The issue I see if you rename all your components is that if you are also to rename the tables, then it will impact your flow that relies on specific table names if I'm not mistaken. That's possible but would require a bit more work to adapt the components.

If you want to know more about good practices related to Solution management, I would also suggest to ask question in the Power Apps - Dataverse forum, you might have good ideas from experts there 🙂

[RichardUchytil]

AH, they are references and not copies.  Good to know.  Thanks again for the great info!  🙂