Dynamic Data Source

[clau0289]

I have created an app for a certain SharePoint site. I am using this same app for other SharePoint sites that have the same structure (tables, columns, etc.) To do this I know have to save the app with another name and replace the data source manually inside the app editor. It would be perfect to have just one single app where I can give the SharePoint site url, or site tables when opening the app.

An idea that comes to my mind would be to have the user select the SharePoint that he wants to connect to and do the data source connection relative to the user's choice.

[JC75NATS]

Yes being able to use patch which uses a variable would equally solve this. A user selects at Powerapp start there department - and that is stored as a variable which means the list/document library you want to then patch to can be placed as a variable in the path formula.

We have an app that is used for multiple Sharepoint site collections that have the same lists set up - but we have to create and consequently any updates to app have to be duplicated. Being able to have one app, that user selects the site they wanting to connect to would mean we deploy one app that can right to which ever Sharepoint list that is then specified in the library.

[mcharing]

This is much needed. I have the same App for all my customers but the SQL database for every customer is different. Now I have to open the open and replace all connections to the different tables that are being used. There must be an easier way. 

[clau0289]

Hey powerapps staff! Any news on this?

[LuukJ]

Much needed feature to be able to push a template from development to multiple production environments (which all have the samen structure, but a different SQL data source). 

[kevinlrak_csu]

I absolutely agree with this. Failing to provide dynamic data source support violates the basic open/close software engineering principle. You shouldn't need to modify the app in order to use it in a new, practically identical, environment.