You’re offline. This is a read only version of the page.
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:
...
...
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?
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.
@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
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"
@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.
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.
#1
WarrenBelz
791
Most Valuable Professional
#2
MS.Ragavendar
410
Super User 2025 Season 2
#3
mmbr1606
275
Super User 2025 Season 2
Share
Report
All responses (
Answers (
