287
Dear Community,
there are 3 managed solutions installed on my prod environment. I want to create a model-driven app, which uses entities all three solutions. Should I create a new solution, which contains just the model driven app? I have a development and production environment, so my idea would be to create an unmanaged solution on my development env with the model driven app and import it as managed on the production environment.
Thank you!
That makes sense. Now that I read your link, I've run into that, too. I wonder if the "fix" is the same... In any case, I think your way is the way most likely to not create exotic failure methods. It stinks that you can really only work on one solution at a time if it affects the app. I'm going to bookmark this to look into in the future. I'm an old coder, and playing with an xrmtoolbox extension might be a fun side project. You won't be the last person to have this issue.
Thank you for your answer. This link got me thinking: crmtipoftheday.com/.../ as well this plugin: www.xrmtoolbox.com/.../
I experienced difficulties with the following scenario:
* Unmanaged solution A with model driven app and is exported from dev and import into production as managed (all fine)
* Unmanaged solution B provides only additional entites. Solution B is exported as managed and imported into production.
* Unmanaged solution C adds the model driven app from solution A and modifies is. Solution C is exported as managed and imported into prod.
Now, when I open the model driven app on my development environment it looks fine. However, when I import solution A into prod the model driven app sitemap looks different compared to when I import solution C. It seems to me, that as soon as I added the model driven app of A into C the state of the app froze as is in solution A. That's why I am thinking about add a solution with just a model driven app to put on top of all solutions.
Its an interesting question. I think you will find that manageable. The part that challenges the traditional solution model is that now if you make changes to one of underlying solutions, you have to change the app solution as well. I guess the other way to do it is to put the app in all of the solutions so that if you change that solution, you can change the app in that solution. The app really lives on its own in each environment as a single app, so it should stay up to date across solutions, but I haven't verified that behavior in real life.
After thinking about this some more, I'm not sure that in either case you will be able to change two base solutions in ways that affect the app at the same time, safely.
In the App Isolated case, if you are making solution changes to two of your base solutions, the app solution can't be deployed until both base solutions are deployed. Or another way to say that is that you can only change one base solution at a time if you want a clear dependency path.
In the App in All case, you're going to run into the same problem because there's really only one App. Although your changes "should" technically be isolated by solution, when you go to export the App in one solution it is still going to have all of the other solution's dependencies attached to it.
Cool problem. Let me know how you solve it.
Brett
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
