Dataverse Tables with LookUp Columns Force Inclusion

(1) Share

Report

Posted on by IPC_ahaas

1,149

Creating a solution with a LookUp Column to a main table for all our locations works great. But when other completely unrelated solutions also use that table, all the Solutions require all the related tables to be included.

This is madness as it will require all my Solutions to have all tables in all my Solutions. Am I missing something or should I be avoiding LookUp columns?

Categories:

Power Platform Build Tools

All responses (1)

Answers (0)

Suggested answer

FLMike 23,258 on at

Like (0)

Report

Dataverse Tables with LookUp Columns Force Inclusion

Hi,

No what you said isn't true. When you make a change, it belongs to you and your solution unless someone takes a dependency on your solution in which case whatever change you made to the table is there.

Important to NOTE, if you only plan to add things DO NOT add the table and then say ADD all the other stuff (metadata and fields) because then you are going to cause a problem.

Just adding the table, then add your fields, so if someone just took a dependency on the default system (meaning no other dependencies) they wont see your field or be required to use it.

If this helps you please mark as the answer.