I wanted a proper definition of "what is a customization?" and how to visualize it?
Why is a customization like adding column to a table not isolated across solutions? If adding column to a table not considered customization, then what is considered customization, what documentation did you refer to improve your understanding of a customization?
Here is a question:
1. Is adding "dummyColumn" to account entity in solution S1. And published the table and customizations in solution s1.
2. I created a solution S2 and I am adding table "account" in solution s2, why does account table have "dummyColumn" in S2? I thought that customization of adding a column to an entity was isolated to solution S1.
Are you using any tools or docs to make these ideas/concepts clearer?
Your understanding is not correct - things are not isolated in the way you currently believe.
(Note: the below is a simplified explanation)
In an environment/instance that is the source environment, each Solution you create is just a container to group things together, either for making working with things easier or because you intend to move your changes to another environment. All of your updates in the source environment are to the unmanaged layer, and the solutions you create in the source are unmanaged solutions (when you come to export, you can export as Managed or Unmanaged) - i.e. there is no 'isolation' per se.
What you can do with your solution is only have a subset of items in them (but changes to the items will reflect in the unmanaged layer and so potentially impact other things), and so only move a subset of items to another environment.
If you move a Solution to another environment, things depend on if the solution is exported as a Managed or Unmanaged Solution from the source. If you import an Unmanaged solution all of the changes in the Solution are merged into what is called the unmanaged layer in the target environment (and there is no undo, other than restoring a backup). If you import a Managed Solution all of the changes in the Solution are layered on top of other previously imported Managed Solutions - with the imported layered items masking pre-existing items with the end user seeing the latest imported version (with managed you can remove the solution and the other, earlier, managed solutions will still be there).
Now that is the simplified explanation (as there are other side-issues that can arise like having an unmanaged layer sitting above your Managed Solution that you just imported and it sitting above one or more of your items, and dependencies)
Ideally you are exporting as managed solutions, and for a next version updating that same solution in the source and importing it as an update.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
2
Share
Report
All responses (
Answers (
