When a related entity is added to a solution because of a single required component, the entire entity is added instead of the one component.

(0) Share

Report

Posted on by Power Platform Comm...

When using the Power Apps Maker Portal to manage solutions for D365 entities, I have noticed entire entities added to the solution when only a single component should be added.

A common scenario is when an entity such as Contacts is a part of a solution and a relationship is added into the solution that references another entity, e.g. Contacts:Accounts N:1. When this is done, the 1:N Accounts:Contacts reltionship should be added to the solution which adds the Accounts entity. Desired behavior is that the Accounts entity is added with only the one component. However, the Power Apps Maker Portal will add the Accounts entity with all components. This is very undesired and can be quite dangerous when importing the solution to another environment.

All responses (6)

Answers (0)

Power Platform Comm... on at

Like (0)

Report

RE: When a related entity is added to a solution because of a single required component, the entire entity is added instead of the one component.

Correct this is a known issue affecting both classic and unified interfaces
Power Platform Comm... on at

Like (0)

Report
RE: When a related entity is added to a solution because of a single required component, the entire entity is added instead of the one component.

@ChadAlt This is part of what I have published in our team Wiki for customisation solution management guideline. Hope it helps

Be careful not to let the system automatically add related components in the following scenarios
Select “No, do not include required components.” option for Missing Required Components prompt when the component is added to the solution. (in classic solution explorer)
Creating/updating the relationship or creating a lookup field (which creates the relationship) in the solution, make sure that entities from both sides of the relationship are in the solution. If one of them is missing out, add the missing one into the solution without any component to prevent from being added automatically by the system.
When the existing form of the entity is added, related Business Rules are automatically added. Those Business Rules which are not modified should be removed from the solution
Mobile Offline Profile should be exported/imported as a separate solution. System will automatically add the related components when the solution with Mobile Offline Profile is exported
Power Platform Comm... on at

Like (0)

Report

RE: When a related entity is added to a solution because of a single required component, the entire entity is added instead of the one component.

agree, it is a pain, but you can avoid that by first adding the related entity to the solution with only the selected components, then create your relationship or lookup field.

See below example: I added the contact entity to my solution with no selected components, then created a relationship with a custom entity, after that the only subcomponents of contacts is the new relationship and lookup field.
Power Platform Comm... on at

Like (0)

Report

RE: When a related entity is added to a solution because of a single required component, the entire entity is added instead of the one component.

Hi Joel,

Thanks for the reply. The biggest issue is when creating a new lookup field, because it automatically adds entire related entity to the solution when using the new maker portal rather than prompting. It's been quite a pain point for our team. I'm sure it's on the Microsoft backlog somewhere, but I wanted to raise it myself in case.

- Chad Althaus
Power Platform Comm... on at

Like (0)

Report

RE: When a related entity is added to a solution because of a single required component, the entire entity is added instead of the one component.

This is a known issue in both the classic and modern solution experience. If you add an entity and it prompts you to add a related entity, clicking yes will add the whole entity. Say no and manually add the parts you want to add to your solution, or add the child entities first selectively, then add the parent.
Linn Zaw Win 3,407 on at

Like (0)

Report

RE: When a related entity is added to a solution because of a single required component, the entire entity is added instead of the one component.

For me, I experience the same issue in the classic solution explorer as well. It happens when I create the lookup/relationship and the other entity of the relationship is not in the system. When the system automatically adds the entity, it either adds without any component (for some entities) or adds the entity with all components.

I just try to make sure that both entities are in the solution when I create lookup/add relationship in the solution. (if one of them is missing out, I just add the entity into the solution without any component to prevent from being added automatically by the system)