
Hi all,
I found that we cannot add 1:N relationship to a solution.
After select and click finish, nothing will be added.
The only thing we can add 1:N is to go to the related entity then add lookup field and N:1 relationship. The 1:N will be added automatically. However if we go to the related entity and add all assets, the 1:N relationship will not be added into solution. If we select "Add required Components" when adding related entity, all assets for this entity will be added into solution but not only the 1:N. That is not what we want. That logic does not make sense to me.
And I found another thing is even we do not add 1:N relationship, we can still deploy the solution to other environments. The 1:N relationship will be created automatically. And no matter we deploy the 1:N or let the system create 1:N, the entity relationship ID is always different.
So my question is:
When we create a new lookup field, do we have to add the 1:N in the related entity? Is there any issue if we do not add the 1:N relationship and let the target environment to create it?
Hi Kevin,
Could you share more screenshots about your issue?
Here is what I did by following your description.
1. Create a new solution.
2. Add Account and its OOB contact_customer_accounts 1:N relationship to the solution, after clicking the finish button, Contact was added into the solution accordingly.
3. Create a new 1:N relationship between Account and a custom entity manually, while the related custom entity isn't added, so there are still two entities in my solution.
For your questions:
1. The 1:N will be created automatically when we create a new look field the child entity.
2. What the issue you refer to? Would it refer to behavior that the entity relationship ID will be always different whatever the relationship is deployed by yourself or created by System?
I think issue would only occur if the previous entity relationship ID is used by customizations.
Regards,
Clofly