Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Unanswered

Add 1:N relationship to solution

(0) ShareShare
ReportReport
Posted on by 160

Hi all,

I found that we cannot add 1:N relationship to a solution.

pastedimage1608171311389v1.png

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?

  • cloflyMao Profile Picture
    25,208 on at
    RE: Add 1:N relationship to solution

    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.

    k1.JPG

    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

Under review

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.

Helpful resources

Quick Links

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,459 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 233,066 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Product updates

Dynamics 365 release plans