Hi all,
I’m running into an issue with solutions and Dataverse table relationships/dependencies and I’m hoping someone can sanity-check what I’m seeing.
Scenario
- I have a Core Data solution that contains a custom core table: Customer (intentionally separate from the standard Account/CDM tables).
- I have a separate solution for another app which contains a custom table: Promotions.
- In the Promotions table, I created a lookup to the Customer table.
- I left the lookup/relationship settings at default (referential, standard behavior).
Expectation
- Promotions solution would depend on Core Data solution (because Promotions uses Customer via lookup).
- I would still be able to export/maintain the Core Data solution independently.
Actual behavior
- After creating the lookup relationship:
- Solution dependency checks show that Customer (Core solution) is somehow dependent on Promotions.
- As a result, I can’t export the Core Data solution on its own anymore unless I include the relationship (or other components) that now pull in Promotions.
Question
Is there a recommended pattern to prevent the core table solution from becoming dependent on the feature solution that references it?
Any guidance (or links to best practices) would be appreciated—this seems like it could be a common “core tables shared across solutions” scenario.
Thanks!
(EDIT: I added the core data tables to the core data solution without selecting include all objects and only selected the columns, keys, business rules, and core relationships, but now the solution is showing that the tables themselves are not in the solution even though I can see them in the solution objects. I tried adding everything except for the promotions relationship in question, but I get the same result)
