Answered

Solutions Require Lookup Table Relationships In Solution Why?

(1) Share

Report

Posted on by IPC_ahaas

1,387 Moderator

Is it normal for my Solutions to require adding ALL tables that are connected to each other? This is causing me to add tables unreleated so my Solution because they have share a Lookup with another table.

Example:

Solution A

Table A

Table B

Solution B

Table C (lookup on Table A)

Before I can deploy Solution A, it requires that I add Table C to the Solution! Even though the Solution has nothing to do with that.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Nandit 1,568 Moderator on at

Like (1)

Report

Hi IPC_ahaas,

Yes, it requires you to add everything.

Kind regards,

Nandit

Was this reply helpful? Yes No
IPC_ahaas 1,387 Moderator on at

Like (1)

Report

Is it reasonable to avoid lookups and table relationships for this reason? I will soon find myself with dozens of Solutions all with the same tables because... because?

Was this reply helpful? Yes No
Suggested answer

Michael E. Gernaey 53,369 Super User 2025 Season 2 on at

Like (1)

Report

Hi

So let's clarify something. If you create a Table and then make a change, like adding a lookup, it effects BOTH tables. So yes you have to add them both.

You Do NOT have to add ALL the properties of the table, just the lookup you created

The reason its required is, how would the next system know anything about the relationship, if you aren't actually exporting the changes because you dont want to add the Table...

Its not an issue with the tech its an issue with your understanding of how it works.

Solution B

Table C (lookup on Table A)

Before I can deploy Solution A, it requires that I add Table C to the Solution! Even though the Solution has nothing to do with that.

Of course it does because Lookups are bi-directional. There is a change to each table to support the relationship. This is just a knowledge lack on your part. So when you say they aren't related, thats.... not.... true...

I would do some more learning on Dataverse and how Relationships work.

Was this reply helpful? Yes No
IPC_ahaas 1,387 Moderator on at

Like (0)

Report

You Do NOT have to add ALL the properties of the table, just the lookup you created

Ah! That is a distinction I haven't come across yet.

how would the next system know anything about the relationship, if you aren't actually exporting the changes because you dont want to add the Table..

That's my whole point, it doesn't need to. If the relationship didn't work at all, that would be just fine, because the solution in question doesn't even use it. It would be nice if I can include only the columns from the related table I need, but I have found it spider-webs out. So my Solution could end up with 10 tables when it really only uses 2.

Was this reply helpful? Yes No