Maintaining Closed Won/Lost Stages in Dynamics 365 for ETL Processes

(0) Share

Report

Posted on by CU06101115-0

In Salesforce, whenever an opportunity is closed as Won or Lost, its stage is automatically updated to “Closed Won” or “Closed Lost” respectively. However, in Dynamics 365, this behavior is different. When an opportunity is closed, the stage does not change—it remains in the stage where the opportunity was before closing.

I need to run ETL processes on Dynamics CRM. My ETL code was originally written for Salesforce and relies on the functionality where the stage is updated to “Closed Won” or “Closed Lost” upon closing.

To handle this, I am considering modifying my pre-ETL connector code to assign an assumed stage to the opportunity when it is closed as Won or Lost.

What other possible approaches can I take to solve this problem without heavily rewriting my ETL code?

Categories:

Dynamics 365 general

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Tom_Gioielli 2,206 Super User 2025 Season 2 on at

Like (0)

Report
Maintaining Closed Won/Lost Stages in Dynamics 365 for ETL Processes

I'm assuming you are referring to the stage on the Business Process Flow? I tend to avoid using the BPF for reporting purposes, as it often relies heavily on user updates which are not always done. I would approach your requirement in one of the following ways:

Don't use the BPF at all. Use the [Status] and [Status Reason] fields directly on the Opportunity which should give you the information you need.

Write a workflow or cloud flow that triggers on close of the Opportunity, and that updates the stage of the Business Process Flow automatically. In this situation, I prefer a D365 workflow as you can trigger it off status change of the related Opportunity and it is easy to use.

Honestly, using the Status fields on the Opportunity should cover everything you need from a reporting perspective for Closed as Won or Lost.

Was this reply helpful? Yes No