Failing Pipelines

(0) Share

Report

Posted on by sasrsc

678

ImportAsHolding failed with exception :The dependent component EntityDataSource (Id=bd2edd71-92c3-4c7c-9941-d22c4bc928f1) does not exist. Failure trying to associate it with Entity (Id=829c37ee-6cdf-4f32-ab0a-9d54fe22cf0e) as a dependency. Missing dependency lookup type = PrimaryKeyLookup.

This solution has 17 tables including dataverse standard and virtual tables.
Most of the tables have at least one lookup.

I know it's giving me a clue and mentioning 2 different id values, but how can that help me pinpoint the issue as I have no idea what entity that is referring to...
When I do...

https://make.powerapps.com/environments/xxxxx my env xxxx/entities/829c37ee-6cdf-4f32-ab0a-9d54fe22cf0e
https://make.powerapps.com/environments/xxxx my env xxxx/entities/bd2edd71-92c3-4c7c-9941-d22c4bc928f1

I get back "That page can't be found"
How can I help myself here and troubleshoot this.... This is a large solution... spent the last 3 days working on it.

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

MichaelFP 1,966 Moderator on at

Like (1)

Report
Copy link

Link copied!
Based on what you write, it looks like that are missing a lookup field, try to remove the table and add it again, and include all components.

Another thing that you can do it is go get the ID
bd2edd71-92c3-4c7c-9941-d22c4bc928f1

and retrieve the information of solution component type from the table SolutionComponent. Whit that information you can try to add in your solution using the action addSolutionComponent action

If my answer helped you, please give me a thumbs up (👍). If solve your question please mark as answer ✔️. This is help the community.

Was this reply helpful? Yes No
Suggested answer

sasrsc 678 on at

Like (1)

Report
Copy link

Link copied!

Thank you for that suggestion. This is a pretty large solution (by my standards) and helping to identify the missing resource was truly a case of trial and error. Eventually I determined I was missing the Virtual Table Data Source for one of my virtual tables. It truly was an effort of patience to go through each entity and try and figure it out. In this case I recreated the Virtual Data Source and that solved the issue.

I actually opened a ticket with MS on this and they didn't have an easy way either.

Was this reply helpful? Yes No