Greetings, all. I have a couple solutions I want to deploy from a Dev environment to a Production environment. One is a "Core" solution that contains tables that will be referenced/used by numerous other solutions. The other is a specific application solution that has its own tables + references tables in the Core solution.
I tried to this using the new Pipelines feature but am getting validation errors on my deployment related to Missing Dependencies.
I checked, and the dependencies in question are all "child" tables that are related to the "parent" table via many-to-one lookups.
Am I not able to deploy solutions because these tables are referenced by other tables? If yes, how in the world does a person deploy Core solutions and then deploy solutions that reference them???
An alternative way to ask this would be: is it possible to add relationships to a table stored in a different solution WITHOUT it creating a dependency in that other solution? Here's an illustration:
Solution A:
Table1
Table2
Solution B:
DataTable (References Table1)
I want to deploy Solution A first and then Solution B, but the reference in Solution B is preventing me from deploying Solution A. Is it possible to add something for Table1 to Solution B in a way that it lets Solution A move without issue?
Was this reply helpful?YesNo
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.
455
Share
Report
All responses (
Answers (
