Unanswered

Unable to apply Upgrade on managed solution

(1) Share

Report

Posted on by Community Power Pla... Microsoft Employee

We're having some issues migrating a few solutions from our Development to UAT environment as a managed solutions. The new solution versions are correctly installed with the "_Upgrade" suffix but the deletion of the previous version fails.

Our first solution contains the out of the box Business Process Flow (Lead to Opportunity BPF) with some customizations to it. The Upgrade holding solution has been installed but the Apply upgrade portion fails with the error: Message: Workflow uninstall: FAILURE, workflow id Message: Workflow uninstall: FAILURE, workflow id 919e14d1-6489-4852-abd0-a63a6ecaac5d category BusinessProcessFlow name Lead to Opportunity Sales Process Detail: category BusinessProcessFlow name Lead to Opportunity Sales Process Detail: ........

BusinessProcessFlow name Lead to Opportunity Sales Process ---> Microsoft.Crm.CrmException: Attribute - {ATTRIBUTE NAME} in the XAML is invalid

The attribute doesn't exist in the xaml we pulled for this BPF (verified in the solution.zip and via an web api call to the process entity) or in the default solution or our source/target solutions.

Our second solution failed to apply an upgrade because a solution-aware power automate was removed. The "delete" functionality seems to be failing for that component. The error returned is: Message: Workflow uninstall: FAILURE, workflow id {GUID} category BusinessProcessFlow name Lead to Opportunity Sales Process Detail:

We are able to apply an update but our ideal behavior would to apply an upgrade so we can remove unused components from our target environment.

We have made a ticket with microsoft and have been waiting for a response for some time now.

Thanks in advance for insight on this.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (5)

Answers (0)

Sort by

DavidNM 12 on at

Like (0)

Report
Copy link

Link copied!

This has also been happening to me with two different solutions after editing business process flows.

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (0)

Report
Copy link

Link copied!

It doesn't seem to be your issue from the error message there, but I should point out that BPFs are not just the BPF component; they also generate a table and columns and a relationship to the record where you put the BPF. If you are trying to drop the BPF but haven't dropped the associated schema as well, you will get dependency failures.

Was this reply helpful? Yes No
DavidNM 12 on at

Like (0)

Report
Copy link

Link copied!

I am aware of the linked entity. I was not dropping the BPF, just updating it, in both situations. Although it is a managed solution, my work around in our UAT environment was to edit the BPF manually in UAT, and then ran the import again. This succeeded. Not ideal as it involves a manual edit of a managed solution. That said, I regularly do this anyway, as changes to forms, view etc. in Dev frequently never get deployed successfully in UAT or production environments, and must again be manually applied via the Default solution.

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (0)

Report
Copy link

Link copied!

Yeah, I figured that wasn't your problem but wanted to post it there for anyone in the future who finds your post because they don't know about the schema interplay.

I've seen others posting in here lately about solution migrations not being subtractive... Are you using the make.powerapps interface for your imports? Have you tried using the Classic UI to do the import to make sure it is giving you an Upgrade and not an Update?

@frick-brian was reporting similar non-subtractive solution migration in a post over here and had determined that it only happened when he used the PA import as opposed to classic.

Was this reply helpful? Yes No
priyanka1231 2 on at

Like (0)

Report
Copy link

Link copied!

Workflow uninstall: FAILURE, workflow id 1b4af77c-41a9-eb11-b1ac-000d3a1b48db category ModernFlow name GenerateReport
facing this issue while deleting of managed code review tool help me out

Was this reply helpful? Yes No