Showing results for 
Search instead for 
Did you mean: 
Helper II
Helper II

Ability to re-configure the site address and list name for flows during import/ copying of flow

Good day All,

I work with SharePoint lists where a new item kicks off a Flow. I usually test/ demo the Flows on a separate site, then I create a copy in the same environment or export/ import Flows to another environment if necessary. Each time, I have to go into each flow and change the Site Address and List Name to refer to the correct one on the production site. My Flows are very lengthy and sometimes, changing these values mess with the lower parts of the Flow, and I end up having to edit the values of each action as though I'm rebuilding it from scratch.

Is there a way to change this during import/ copy of a flow?



Accepted Solutions
Resident Rockstar
Resident Rockstar

you could open the json files in the export and do a find/replace that way perhaps

View solution in original post

Continued Contributor
Continued Contributor

Unfortunately, while flow is a great tool, it's a little weak in the areas of application life cycle management, such as deployment, among other areas. The references to SharePoint sites and lists are hard coded into each action, and cannot be replaced with some sort of variable. This means that switching sites or lists requires what you mentioned, a long process of updating and re-testing the flow. 


Since the flow will need to be tested in production at some point (at the very least, after it's been deployed and reconfigured), then I'd suggest making changes to the list and flow as needed as to enable testing in production. For example, in flows that send an email or and approval to an address based on a choice field from the list, I'll add a choice that is used for testing to ensure the email gets routed to the appropriate test user. 

Resident Rockstar
Resident Rockstar

you could open the json files in the export and do a find/replace that way perhaps

View solution in original post

Hey @Mike2500 ,


Thank you for your response. I've tried to make this process as easy as I could with respect to testing. I guess I'll just have to go through each Flow after the copy/ import and do it the long way :(.

I hope eventually Flow can put something in place for this.

Thanks again 🙂

Hey @Gristy ,

Good idea. I will look into this. However, I'd have to be careful to not corrupt anything lol. Maybe going through it the long way will be the best method. But thank you for your suggestion! 🙂

Helpful resources

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS Carousel

Sign up for our May 4th event!

May the fourth be with you, join us online!


Experience what’s next for Power Virtual Agents

See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Users online (45,048)