Unanswered

Deploying Solution Requires Related Tables That Are Not Used

(0) Share

Report

Posted on by IPC_ahaas

1,387 Moderator

Maybe I need to change how I'm doing things. Right now, when I deploy a solution, if any of my tables related to other tables - even if my solution doesn't use those related tables - it requires that I add them to my Solution.

I have Production app and an Inventory app. Both use the Site table which has our all location information. My Inventory app requires that I have the table meant only for Production, because it relates to the Site table. Eventually I'll be at the point where every Solution I have that uses the Site table, will need every table for every unrelated app included! This can't be right and there must be something to change this.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (8)

Answers (1)

Guido Preite 1,488 Super User 2024 Season 1 on at

Like (0)

Report

"even if my solution doesn't use those related tables" doesn't mean if you use it or not, if they are related (for example there is a lookup or a N:N relationship) and if this table is not inside the target system it will give you an error on deployment.

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

Like (0)

Report

Exactly! So should I be making duplicate tables for my Solutions so that every Solution doesn't have every table? Or start using hard coded values?

Was this reply helpful? Yes No
Guido Preite 1,488 Super User 2024 Season 1 on at

Like (0)

Report

I don't know how your solution is structured and it's a too much generic question to answer on how you need to design the solutions in your environment

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

Like (1)

Report

More generalized then - if two Solutions (Solution 1, Solution 2) their own tables (Table 1, Table 2), but those two tables share a common relationship to another table (Table 3) - how do you prevent Solution 1's table (Table 1) from being included in Solution 2? Currently, because Table 3 is related to both Table 1 and Table 2, all three tables need to be in both Solutions.

If Table 1 and Table 2 had thousands of records (which they will) - this will muddy the list of items within a given Solution, getting worse with every new Solution that uses Table 3.

Was this reply helpful? Yes No
Verified answer

Guido Preite 1,488 Super User 2024 Season 1 on at

Like (0)

Report

you cannot. If you are deploying Solution 2 to an environment where Table1 is not there you get the error (as happening now).

Generally the number of records is irrelevant to how the solution is designed.

If you need to develop Solution 2 as standalone, you should build it inside a clean environment, not one where there are other solutions that may be connected to your Table 3.

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

Like (1)

Report

MAN that sucks.

Was this reply helpful? Yes No
BEJONES 15 on at

Like (0)

Report

Realize this is now an old question, but best practice for us is to deploy that shared, common table (Table 3 in your example) as part of a Base Solution. Then solution 1 and 2 can be developed and deployed separately from each other into the same environment where Base Solution lives, and without picking up any dependencies on each other.

just be EXTRA sure to get yourself into a triangle dependency from hell.

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

Like (0)

Report

I ended up restructuring my tables so there are no lookup columns and this resolved the need to include them into the Solution.

Was this reply helpful? Yes No