Power Platform Community Forum Thread Details

Hello,

I have developed a PDP application using Power Apps (Canvas App), SharePoint, and Power Automate in my organization’s environment. I now need to handover this application to a client, so that they can import and use it in their own tenant without issues. And if I downloaded stp file of list so how it imported by client.

I am looking for clear, end-to-end guidance on the correct and supported way to export and hand over the following components:

Power Apps (Canvas App)
Power Automate flows (inside a solution)
SharePoint lists used by both the app and the flows

The main challenges we are facing are related to SharePoint list export:

In some SharePoint sites, the “Save list as template” option is not visible.
Sometimes the List Template Gallery does not appear under Site Settings.
Because of these issues, we are unsure of the best and most reliable approach to package SharePoint lists for client import.

Our goal is that the client should be able to import everything into their environment and use the application without manual fixes or broken connections.

Could someone please explain:

The recommended approach for exporting SharePoint lists for client handover
How to handle scenarios where “Save list as template” is not available
Best practices for exporting and importing Power Apps and Power Automate flows together with SharePoint dependencies

Any detailed explanation or reference documentation would be greatly appreciated.

Regards,

Employee (1).stp

Categories:

Power Apps Pro Dev & ISV

Hi,

There should be a better way to do what you are looking to do with the SharePoint Lists that are part of your project like what can be done with DataVerse tables, but there isn't. SharePoint is treated like the red headed stepchild of the Power Platform when it shouldn't.

For your Solution, I am assuming you are using an approach similar to what Share Young describes here:

Power Apps and Automate Solutions and Environment Variables for SharePoint

You use Environmental variables for the SharePoint Site and SharePoint Lists in your Solution.

"Save list as template" is deprecated on modern sites (which is really unfortunate). It is just not supported.

If you have access to PnP PowerShell, then you should be able to export and import the list schema using:

Get-PnPList -Identity "ListName" | Export-PnPListToProvisioningTemplate -Out "ListName.xml"

Apply-PnPProvisioningTemplate -Path "ListName.xml"

This blog post also has some good information on using PnP to copy the SharePoint Lists.

https://www.enjoysharepoint.com/export-and-import-sharepoint-online-site-as-template-using-powershell

For a project I worked on where we used SharePoint, we created the lists in a Dev Site and then used SharePoint to copy them to the Production site. This allowed for verification and configuration of the lists. For another project, we used ShareGate (Simplify Microsoft 365 migrations & governance | ShareGate) but that project was also a migration.

There should be a better way to do this. There should be a way to add Lists to a Solution like you can DataVerse Tables. I suspect that the reason it is not there is to cause a pain point to get you to move to Dataverse and thus Premium Licensing.

This community is supported by individuals freely devoting their time to answer questions and provide support. They do it to let you know you are not alone. This is a community.

If someone has been able to answer your questions or solve your problem, please click Does this answer your question. This will help others who have the same question find a solution quickly via the forum search.

If someone was able to provide you with more information that moved you closer to a solution, throw them a Like. It might make their day. 😊

Thanks
-Mark