Microsoft Dynamics 365 | Integration, Dataverse...

Stage ID ‘f6d37cba-65ca-41b7-a5d8-f90a01a13a45’ is not present in Business Process.

(1) Share

Report

Posted on by AT-30121247-0

I had to delete a certain stage in dev environment and after deploying to prod, there were still records left which had that certain stage id as active stage id. When I try to change the active stage, it says I'm trying to change an inactive process which is not possible. Any ideas how to fix the broken records? They just have no BPF now. Records in other stages work fine, and newly created records work as well

Categories:

Dynamics 365 general

I have the same question (0)

All responses (3)

Answers (0)

Mansi Soni 8,933 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hello, Can you clarify which Dynamics 365 Products are you using like D365 Business Central, CRM, F&O?

Regards,
Mansi Soni

Was this reply helpful? Yes No
AT-30121247-0 4 on at

Like (0)

Report
Copy link

Link copied!

@Mansi Soni I am using D365 CRM, specifically a Model Driven Power Apps application using Dataverse as the database.

Was this reply helpful? Yes No
Suggested answer

iampranjal 67 on at

Like (0)

Report
Copy link

Link copied!
Hi there,

This is a common issue when a BPF stage is removed in Development and the change is deployed to Production while active records are still sitting in that specific stage.

Essentially, the backend record for the Business Process Flow (e.g., the opportunitysalesprocess table) still has its ActiveStageId column set to the GUID of the deleted stage. Since the metadata for that stage no longer exists in the system, the form cannot render the process bar and throws this error.

Here are two ways to fix the broken records:

Method 1: The "Clean" Fix (Update the Stage via Flow)

You need to force the ActiveStageId to point to a valid stage (e.g., the first stage or the one prior to the deleted one).

Get a valid Stage ID: Open a working record, use the browser console (F12), and run Xrm.Page.data.process.getActiveStage().getId() to get a valid GUID.

Create an Instant Cloud Flow:

List rows: Query the BPF Table (e.g., Opportunity Sales Process, not the Opportunity table).

Filter: Filter for the records related to your broken main records.

Update row: Update the ActiveStageId field on these records with the valid GUID you found in step 1.

Refresh the record in the UI; it should now load correctly on the new stage.

Method 2: The "Quick" Fix (Delete the BPF Instance)

If you don't mind resetting the process progress for these specific records:

Go to the Maker Portal (https://www.google.com/search?q=make.powerapps.com) or use Advanced Find.

Look for the table corresponding to your BPF (e.g., "Lead to Opportunity Sales Process").

Find the entries associated with the broken records and Delete them.

When you open the main record again, the system will generate a fresh BPF instance starting at the first stage.

Hope this helps!

Was this reply helpful? Yes No