Share
Report
4Hello,
I currently have a canvas app and an entire solution (a Dataverse table, model-driven app for auditing/version history, dataflows) built in a Development Environment. The canvas app is directly connected to the Dataverse table. I want to be able to use the Development Env for back-end use, app customizations, viewing audit logs, updating Dataverse table from a SQL dataflow daily etc.
I also have a Production Environment, which will only include the canvas-app from the Development Environment, for end-users. I have export/imported the app as a managed solution from the Dev environment to the Prod environment.
My issue is that I want this canvas app to be directly connected back to the Dev environment Dataverse table rather than in its own environment. In the canvas app, under Add Data, I have the ability to change environments and select the Dataverse table from the Dev env, however, I might have to reconnect every item in the app to have a full connection. Is there a fast and efficient way of doing this, rather than going property by property and changing the source?
This is not preferred. If I make any customizations/updates in the Dev Env app I will have to reupload the solution back into the Prod Env.
To summarize, I'd like to use the Dev environment for back-end app customizations/updating and have all of the data stored within its Dataverse table.
The Production environment will have a copied solution of the canvas app for end-users, but I need it to be connected directly back to the Dev Dataverse table and updated every time a canvas app customization is made in the Dev Env App. If data changes are made in the Prod app, I want them to be linked back to Dev Dataverse table, and if data changes are made in the Dev Dataverse table, I want them to be linked back to the Prod canvas app.
If this is not possible, please provide me with an alternative. If clarification is needed, please let me know.
Thanks!
All responses (
Answers (
