Creating a solution with a customization: should I include required components?

(0) Share

Report

Posted on by Joel D

355

Hi,

I am studying how solutions work on CRM.

Let's suppose that we want to create a custom solution on CRM to change a component (relationship) of an entity (Order). We want to publish this custom solution on a "Dev" environment, and later we want to release it on a "Prod" environment. Both these environments already have the main solution with all the main components.
We want to make our custom solution as light as possible, so we include metadata only, without adding required components, because they are supposed to be already in the main solution.
Does it make sense or the required components should always be added?

All responses (3)

Answers (2)

Verified answer

Community Member on at

Like (1)

Report

RE: Creating a solution with a customization: should I include required components?

If your target environment already contains all the components required to run customization, you can definitely stick to the meta use only.

But I would strongly emphasize testing a solution made using meta and one that accommodates all the components to know what difference it brings to the outcome.

I will be looking forward to your response.
Verified answer

CaptJoe 140 on at

Like (1)

Report

RE: Creating a solution with a customization: should I include required components?

No reason to include those required components when they'll be included in the target environments.
Suggested answer

Nya 29,060 on at

Like (1)

Report

RE: Creating a solution with a customization: should I include required components?

Hi,

Please refer to the following section and the image in it to determine which elements need to be included in your solution.

How solutions are applied