Share your ideas and vote for future features

Rfla · ‎08-23-2016

Export/import and change data source as long as the source has the same setup. Edit the data source and keep the app as it is. Reuse the app in a sense. As an example you have a SP product. It is installed on a customer online tenant. Then you create an PowerApp for the SharePoint "list/setup/product". New customer, same SP product installed. Then export/import the app. Change data source and publish to the new customer’s employees.

Anonymous · ‎07-24-2017

Hi all, we want to transport PowerApps between multiple Tenants. This will be a greate feature, because at the moment we are developing our Apps in a "DEV" Tenant and must rebuild it in the "LIVE" Tenant. Another examle, we have some customers with multiple Office 365 Tenants (diffrent companys but the same holding), at the moment we need to build the app from the scratch in each Tenant. Kind regards, Gerrit

JDJR · ‎05-02-2016

The ability for me to export my app and send it over to a customer for them to import into their environment. This will allow me as a developer to design apps for different customers and send over my work once completed. Example: the customer would describe what they want and send me a spreadsheet or a sample database (SQL, Access) of the data. I perform the work and demo what I've done. Once everything is squared away, I can send it over for them to test and then deploy out to their users. After payment of course.

Share your ideas and vote for future features

Change datasource to reuse app (export/import)

Export PowerApps from one Tenant to another Tenant

Import and Exporting of an App

Helpful resources

Native connector for Azure Datalake Gen 2

Advanced Editor for Dataflow

Access Control Improvements for Large Enterprises

URGENT: Ability for Admins to COMPLETELY remove Co...

Importing Managed Solutions with Connections