cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
iperezlemme
Frequent Visitor

Importing Power Platform Solution Error: unprocessed files found

Hi all,

I've been struggling with the importing of a Power Platform solution that consists on the following.

iperezlemme_0-1637180776835.png

 

When importing this unmanaged solution into my UAT environment using any methods (manual import, the Power Platform CLI, Azure DevOps) everything works fine.

 

When importing this unmanaged solution into my PROD environment using any methods (manual import, the Power Platform CLI, Azure DevOps) I'm facing an error.

 

Using both the Power Platform CLI and Azure DevOps Pipelines I get: 

 

Unprocessed files found: /environmentvariabledefinitions/bia_ONOFFFlow_AccessEndpoint/environmentvariablevalues.json, /environmentvariabledefinitions/bia_ONOFFFlow_Signature/environmentvariablevalues.json, /environmentvariabledefinitions/bia_SendToEmail/environmentvariablevalues.json

 

 

Using a manual import in the classic view (the modern view gives my a non-descriptive error) I get the error, which is logged in the attached xlsx file. 

 

I all three cases the error points the same thing, some unprocessed files, that refer to my environment variables. In the production environment this variables don't exist yet. 

 

It's worth pointing out that when using CLI and DevOps, I'm using a deployment settings json file that has the variable values for that specific environment.

 

Thanks in advance,

Ignacio

 

2 REPLIES 2
RickUK
Regular Visitor

Did you sort it?

Difficult to comment across 2 environments, especially with unmanaged. 
I've been doing a fair bit of solution moving recently and using a sandbox to reset environments is handy.
Have you tried importing as managed?
Obviously the Env Variables don't exist yest in Prod if you never imported but you must have a idea as to what the variables and files refer to in your dependency schedule.  

iperezlemme
Frequent Visitor

Yep, forgot to upload my resolution. What I ended up doing was deleting those environment variables that were causing the problems. After doing so, the issue was solved. 

Helpful resources

Announcements
Power Platform Call June 2022 768x460.png

Power Platform Community Call

Join us for the next call on August 17, 2022 at 8am PDT.

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Users online (3,045)