Answered

Powerapps Solution - Pipeline Error - Missing Dependency Table Object - Object is Present

(1) Share

Report

Posted on by CB-08081625-0

Hello,

I am trying to deploy a solution to another environment and in the pipeline deployment I receive a "Missing dependencies" message (Fig1). In my solution I have correctly added the table object (Fig2). Note I have also included all fields and meta data.

Any ideas what to do to fix this?

Fig1 (70 objects):

Fig2:

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

MichaelFP 1,943 Moderator on at

Like (1)

Report
Copy link

Link copied!
try to use the action AddSolutionComponent to include this table again.

here a sample

// Parameters var parameters = {}; parameters.ComponentId = null; // Id of the table parameters.ComponentType = 1; // Edm.Int32 parameters.SolutionUniqueName = "YourSolutionnAme"; // Edm.String parameters.AddRequiredComponents = false; // Edm.Boolean fetch(Xrm.Utility.getGlobalContext().getClientUrl() + "/api/data/v9.2/AddSolutionComponent", { method: "POST", headers: { "OData-MaxVersion": "4.0", "OData-Version": "4.0", "Content-Type": "application/json; charset=utf-8", "Accept": "application/json" }, body: JSON.stringify(parameters) }).then( function success(response) { return response.json().then((json) => { if (response.ok) { return [response, json]; } else { throw json.error; } }); } ).then(function (responseObjects) { var response = responseObjects[0]; var responseBody = responseObjects[1]; var result = responseBody; console.log(result); // Return Type: mscrm.AddSolutionComponentResponse // Output Parameters var id = result["id"]; // Edm.Guid }).catch(function (error) { console.log(error.message); });

Was this reply helpful? Yes No
CB-08081625-0 20 on at

Like (0)

Report
Copy link

Link copied!

Sorry but where would I put this?

Was this reply helpful? Yes No
CU01100247-0 7 on at

Like (0)

Report
Copy link

Link copied!

Monitoring this post, as I have started running into the same issue. I am working on an app we deployed to Prod 4 months ago, and have been making monthly updates via the same pipeline. Since the introduction of the ALM and new designer for dataverse tables, any new table I try to add to the existing application (which we need for attachment processing) gets the same missing dependency issues you've listed.

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

Like (0)

Report
Copy link

Link copied!

Have you tried selecting "Publish all customizations" under "Objects > All"?

Was this reply helpful? Yes No
Verified answer

CB-08081625-0 20 on at

Like (0)

Report
Copy link

Link copied!

I have tried "Publish all customizations" under "Objects > All" with no luck.

I was able to resolve the issue but not the way I would have liked to. I should have noted that I used XRM Toolbox to copy fields from a main table to the historical table. It seems that in doing so that is what had caused this issue. Reason I say that is I recreated the table directly in Dataverse, rather than copying in XRM Toolbox, I then added the table again to the solution and was able to export without issue.

This is quite frustrating as the tools within Dataverse to manipulate data are so underdeveloped it would be nice to have something that worked.

Was this reply helpful? Yes No