You’re offline. This is a read only version of the page.
451
Greetings, all. Need some direction regarding handling solutions within the Dataverse and finding this to be a bit of a brain-bender. I'm looking to create multiple apps that share "components" (e.g., flows, tables, environment variables). I've been reading the MS docs on segmented solutions and organizing solutions and am struggling to make sense of it.
Here's an example. Let's say I have two canvas apps that both use Dataverse tables. I also have some flows that each app uses. The Process Log flow (#1) and the Customer table (#2) are both used across multiple apps, and #1 is going to be used by all apps.
Should I be creating them all in one solution? But if I do that, how can I then deploy only the changes to one app but not WIP on another (selective deployment)? Or, should I be creating two solutions (Sales App and HR App) but then store the tables and flows in one/two other solutions? Thinking that way because of this MS doc:
Don’t have two different solutions in an environment where both contain tables. This is because there are frequently risks of a single relationship between tables, which creates a cross-solution dependency and causes solution upgrade or delete issues in the target environment at a later point in time.
Of course, I thought the whole idea of solutions was you add everything needed for an app and then deploy it in one fell swoop... 🤔 Whatever I do, I want to ensure with our solutions that:
Basically, I need help! Thanks in advance.
@arpost, always happy to help 🙂
@arpost ,
So am I right in taking that to mean that only the live/published version of a canvas app is what get's used in the exported solution? That is correct
On a semi-related note, how do you handle things like Power Automate flows that don't have a "publish" option? Or have you run into that? If you are working continuously on Flows, I would have those in a separate solutions as they are not affected by dependancy.
| If my reply helped you, please give a 👍 , & if it solved your issue, please give a 👍 & Accept it as the Solution to help other community members find it more. I am primarily available on weekdays from 6-10 PM CT and 5-10 PM CT on weekends. Visit my Blog: www.powerplatformplace.com Visit my YouTube Channel: https://www.youtube.com/@powerplatformplace/videos |
Thanks for the reply, @AhmedSalih! That's helpful. So am I right in taking that to mean that only the live/published version of a canvas app is what get's used in the exported solution?
On a semi-related note, how do you handle things like Power Automate flows that don't have a "publish" option? Or have you run into that?
Hello, @arpost, I usually use one solution if I have multiple apps that are using same tables. If App A is ready for deployment and App is under development for the current iteration, I wont publish App B until it is ready. This way your exported solution include the last published version of App A and most recent working version of App B. Solutions dependency is a pain.
#1
stampcoin
17
#2
ankit_singhal
11
Super User 2025 Season 1
#3
mmbr1606
9
Super User 2025 Season 1
Share
Report
All responses (
Answers (
