Power Platform Community Forum Thread Details

Hello everyone!

I'm having trouble sharing my flow. A few days ago a user asked me to make a flow to make some changes to an Excel file, so I used Excel Business actions such as Run script, list rows present in a table, create worksheet, create table and get worksheet. However, the user requires that this flow be his "property" and that I don't have access to the folders or anything like that because they are confidential documents. The problem is that when the user copies the flow or wants to import it, it throws up different errors. I've tried to fix it in different ways. One of the errors it throws up is that the scripts have not been found but they have already been shared with the user. Some folders have even had their path changed and I tried to remap them but it still doesn't work.
I would really appreciate your help if you could provide me with any kind of solution. Thank you in advance.

Categories:

Building flows

You will either need to create a Solution package in the Power Apps menu or modify your flow to avoid references for the legacy import method.

Go to Power Apps home & choose Solution on the left-side menu, create a solution, and pull your flow & related connections into the new solution, then export it as an unmanaged solution & have him import it.

In your flow create a placeholder Compose action at the start & anywhere there is a reference to a site, document library, file, table, script, etc insert the Compose dynamic content. This will prevent any references in the Excel actions & prevent any dependencies on sources/files/tables so someone else can import your legacy package without having access to the data you used.

See an example of a template using both import methods here: https://community.powerplatform.com/galleries/gallery-posts/?postid=9f7a7bcf-c88f-ef11-ac20-7c1e525bd67d