Solutions:
A Solution is a container for components that comprise a particular
customization project. By keeping track of all the components of a single
Solution, Microsoft Dynamics CRM can ensure that:
• When a Solution is exported or imported, all components are
transferred.
• Version control is maintained.
• Security specific to the Solution is applied to the correct entities.
Default Solution
When an Organization is created, a Solution is created with it that contains all the
components in the system. This is called the Default Solution. You can customize
the standard components through the Default Solution and even add new entities
or other components to it. The Default Solution (with any customizations) can be
exported and imported to another Organization. This scenario provides similar
capabilities to those in Microsoft Dynamics CRM 4.0.
Managed and Unmanaged Solutions
A Solution can exist in one of two states; Managed and Unmanaged. When a
Solution is first created, it does not have any components and it exists in an
unmanaged state. Unmanaged Solutions are containers that hold references to
components in the organization. As you add existing components, a new
reference to that component is created in the solution.
The fact that unmanaged Solutions contain references to entities and other
components is an important one. It means that all unmanaged Solutions in an
Organization are really just views onto the concrete components. All unmanaged
Solutions can "see" the components and references can be added if desired.
If a Solution must be isolated from others in the Organization, it can be loaded in
a managed state. Unmanaged Solutions are converted to a managed state by
exporting them as Managed, then importing them to the target Organization.
Managed Solution components are kept isolated from the rest of the
Organization, though they can be referenced from unmanaged Solutions. When a
managed Solution is imported, the Managed Properties configured on its
components become active. The Solution designer uses the managed properties
to restrict or allow further customizations to the components. For example, an
attribute of an entity can allow a change of the display name but not of the
requirement level.
More than one managed Solution can be imported into an Organization.
Therefore, the final view of customizations is built from:
• The Default Solution modified by all unmanaged Solutions.
• The first managed Solution.
• The second managed Solution – and so on.
• The System Solution.
A video which help you to understand better which as follows,
A Solution is a container for components that comprise a particular
customization project. By keeping track of all the components of a single
Solution, Microsoft Dynamics CRM can ensure that:
• When a Solution is exported or imported, all components are
transferred.
• Version control is maintained.
• Security specific to the Solution is applied to the correct entities.
Default Solution
When an Organization is created, a Solution is created with it that contains all the
components in the system. This is called the Default Solution. You can customize
the standard components through the Default Solution and even add new entities
or other components to it. The Default Solution (with any customizations) can be
exported and imported to another Organization. This scenario provides similar
capabilities to those in Microsoft Dynamics CRM 4.0.
Managed and Unmanaged Solutions
A Solution can exist in one of two states; Managed and Unmanaged. When a
Solution is first created, it does not have any components and it exists in an
unmanaged state. Unmanaged Solutions are containers that hold references to
components in the organization. As you add existing components, a new
reference to that component is created in the solution.
The fact that unmanaged Solutions contain references to entities and other
components is an important one. It means that all unmanaged Solutions in an
Organization are really just views onto the concrete components. All unmanaged
Solutions can "see" the components and references can be added if desired.
If a Solution must be isolated from others in the Organization, it can be loaded in
a managed state. Unmanaged Solutions are converted to a managed state by
exporting them as Managed, then importing them to the target Organization.
Managed Solution components are kept isolated from the rest of the
Organization, though they can be referenced from unmanaged Solutions. When a
managed Solution is imported, the Managed Properties configured on its
components become active. The Solution designer uses the managed properties
to restrict or allow further customizations to the components. For example, an
attribute of an entity can allow a change of the display name but not of the
requirement level.
More than one managed Solution can be imported into an Organization.
Therefore, the final view of customizations is built from:
• The Default Solution modified by all unmanaged Solutions.
• The first managed Solution.
• The second managed Solution – and so on.
• The System Solution.
A video which help you to understand better which as follows,
No comments:
Post a Comment