You’re offline. This is a read only version of the page.
33
A solution contains a Model-Driven App consisting of that solution's custom tables.
An addon solution contains that same Model-Driven App and adds its own custom tables.
We want this addon solution to be easily imported or deleted, enabled or disabled, in an environment but, once the addon solution is imported, the Model-Driven App is given dependencies that prevent the addon from being deleted/disabled.
This was tested with existing applications and addons from AppSource, but these worked perfectly fine.
The addon was installed and could be deleted whenever, automatically reverting the shared Model-Driven App as needed.
How can we do this with our own solutions and applications? Is this supported or did these apps on AppSource make custom file modifications?
Any helpful insight or advice is appreciated. Thanks
Caching and unmanaged solution leftover artifacts of sorts cause the dependencies to appear when they should not.
A fresh environment with neither the solution nor its addon is needed for it to work. Both must be managed solutions and once the addon is imported/installed, it can be removed just as the AppSource examples have in the past.
Share
Report
All responses (
Answers (
