Unanswered

Solution Import: An error occurred in CreateVariableValue

(0) Share

Report

Posted on by westerdaled

672

Yesterday, I successfully imported a solution with a small number of: connection references, canvas apps , flows and environment variables into our Production environment.

Then I started getting the above error during the final step of the solution import process when I tried a larger solution. So I created a stripped dummy solution that just had environment variables and connection references but this also gives me the error

solutionName_import.xml

Solution import error creating variable value.PNG

I looks like it hasn't even got the environment vars as they are listed below the unprocessed connection references shown in the image above. Anybody seen this issue before?

Update: switched to Classic View and you get a different error albeit with a 7 KB solution file 🙄:

Solution import classic view.PNG

Update2:

The solution did import after all , but I could do with a way of inspecting the environment variables , as these are shown as "unprocessed". The connection refs are all switched off as well

solution import with conn references switched off.PNG

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (0)

Sort by

cchannon 4,702 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Connection References import as 'off' because it is assumed that your references will change between environments. If you do the import through the modern UI, it will prompt you to fix these references during import.

Was this reply helpful? Yes No
westerdaled 672 on at

Like
a
(0)

Report
Copy link

Link copied!

@cchannon

Thanks for clarifying. Having worked with my large solution for a while now , I have noticed the connection references can be brittle esp when changing site and list enviroment variables or pasting actions from another flow. Out of interest is there guidance on the account used to create the ( SharePoint, Outlook etc) connection reference i.e should this be a service account and not the humble consultant's?

Was this reply helpful? Yes No