You’re offline. This is a read only version of the page.
We are unable to promote solutions from our development environment to our test or production environments using Pipelines due to dependencies. We're trying to promote a solution which has apps and tables in the solution that the app requires. When we try to promote the solution, it says that there are dependencies that need to be added to the solution but those dependencies are not being used in the solution that we are trying to promote. They are part of other solutions.
For example, the app in the solution that we are trying to promote adds vehicle mileage to a table called Vehicle Mileage which has a lookup to the Vehicle table. We have included both the Vehicle Mileage and Vehicle tables to that solution. Now, it's giving us an error that we need another table from another solution that also uses the Vehicle table. So solution A uses and includes Vehicle & Vehicle Mileage and solution B uses and includes Vehicle and Vehicle Ownership. When we try to promote solution A to our test environment, it tells us that it needs the Vehicle Ownership table even though solution A doesn't use that table. If we try to add the table to the solution, we get a bunch more dependency errors.
Has anyone ever gone through this? I feel like I'm not understanding how solutions work. In our environment, we have a lot of tables and many are related but we only include the tables in the solutions that use for that specific app and each app has it's own solution. How is this supposed to work? Any guidance would be appreciated.
Hi,
Please check the dependencies in Solution A for each table. If one of them has a dependency to another table which is not in that solution you will receive that error. To solve your problem, only add that dependency and not the entire table. To do that, you can use the Add Existing to add that required dependency.
Share
Report
All responses (
Answers (
140
