Answered

Azure pipeline error with formula (PowerFX) dataverse column

(0) Share

Report

Posted on by Arcadi

Hello,

I have a column with a powerFX formula. If I try to export the solution (as unmanaged) and import it into a new environment using a pipeline, I get the following error:

...

Error: Exception type: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]

Message: Error while importing Formula fields name [solution]_[columnName]Detail:

...

FormulaDefinition file is missing from import zip file: FileName: /Formulas/[solution]_[entity]-FormulaDefinitions.yaml

...

In fact, the "missing" file is in the unpacked solution:

But if I try to export it either managed or unmanaged manually (without pipelines), I have no problem importing it to another environment. I know this feature is in preview, so is it possible that it's a bug?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Arcadi 57 on at

Like
a
(0)

Report
Copy link

Link copied!

After adding another powerFX column and resetting the target environment, now the error is:
"Error: The given key was not present in the dictionary."

Still, no problem importing the solution manually, managed or unmanaged.

Was this reply helpful? Yes No
cjbarnaby 44 on at

Like
a
(1)

Report
Copy link

Link copied!

@Arcadi - we're facing the same issue. However, when you say:
@Arcadi wrote:
After adding another powerFX column and resetting the target environment, now the error is:
"Error: The given key was not present in the dictionary."
I think if you go into the Solutions 'History' tab in make.powerapps.com, and find the corresponding 'Import' job, a more comprehensive/accurate error is captured there (and you might also see it in the ADO pipeline logs, logged as a message rather than an error). This is unrelated to the issue in your original post, but it seems like the latest update to the Build Tools has caused some issues with the way errors are being handled; specifically: non-error messages are being presented as error-level messages (eg "[error]Error: Connected to...[name of environment] ); actual error messages being presented as information-level messages; and this 'The given key was not present in the dictionary' error, which doesn't actually provide details of why the import failed.

Was this reply helpful? Yes No
Arcadi 57 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you @cjbarnaby, I wasn't aware that there was a history tab.
It seems the error is the same:
"Error while importing Formula fields name solution_powerFXcolumnName"

Was this reply helpful? Yes No
Verified answer

David Jenni Microsoft Employee on at

Like
a
(2)

Report
Copy link

Link copied!

@Arcadi @cjbarnaby there were 2 actually independent issues in the pac CLI (which is also the implementation basis for the Azure DevOps PP-BT tasks:
- when packaging a locally extracted solution.zip via `pac solution pack`, any .yaml file with PowerFX was not detected, and thus was missing in the repackaged sol.zip
- the "given key was not found in dictionary" error during `pac solution import` was caused by a new Dataverse status code returned from the DV api.

Both issues should be fixed in the latest October refresh for pac CLI (version >= 1.20.3) and PP-BT (version >= 2.0.10).
Should this still reproe, please file an issue in https://github.com/microsoft/powerplatform-build-tools

Was this reply helpful? Yes No
hsvensson 39 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi!

Running "pac solution unpack" followed by "pac solution pack" on a solution (that imports perfectly by manual export followed by manual import) I get the following error message:

Error: Entity 'X' references formula file '/Formulas/X-FormulaDefinitions.yaml', but file is not included in solution.zip

I am using Microsoft.PowerApps.CLI.1.21.8 for this. It seems like this issue has been reintroduced since the release of 1.20.3.

Was this reply helpful? Yes No