Importing managed solution Dynamics Dataverse into PowerBI does not display the pipeline phase

(2) Share

Report

Posted on by CU09051923-0

Hello,

I have been helping my organization implement Dynamics for Sales tracking (my background is in Mechanical Engineering with decent experience and background in programming and Dynamics).

We have a two-solution approach. Development and Production.

When Development unmanaged env is imported in Dynamics, Pipeline phase (StepName) from the opportunity table is not visible
When Production managed env is imported in Dynamics, Pipeline phase (StepName) from the opportunity table is null

I have looked at the following to troubleshoot this problem.

Production env Pipeline phase is visible via Fetchxml in xrmtoolbox.
Pipeline Phase "is Customizable" field is set to Yes in the under managed properties in the Production env.

All the current data for Pipeline phase in Dynamics, per Fetchxml, is populated and is correct. No missing or incorrect values are displayed

We are using 4 stage tracking in Pipeline phase. 1-Qualify, 2-Develop, 3-Propose, 4-Close

We are populating the Pipeline phases through business process flows specifically two custom flows: Lead to Opportunity Sales Process and Opportunity Sales process

We also have some custom BPFs to track if a stage criteria are met, if so, automation is in place to progress the sale stage.

I am looking forward to some solution that can allow me to read the pipeline phases in PowerBI. If it can be achieved by importing a specific table from Dataverse we can do that. Currently we are importing Accounts, Contacts, Opportunity, Leads and a few custom tables.

Best,

Vickey Kalaskar

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (0)

Muhammad Shahzad Sh... 2,336 Most Valuable Professional on at

Like (0)

Report
Importing managed solution Dynamics Dataverse into PowerBI does not display the pipeline phase

Include the ProcessStage Table:

In Power BI, connect to Dataverse and import the processstage table.

This table holds the stage names (e.g., Qualify, Develop, etc.).

Include the Opportunity Table:

Ensure you're importing the opportunity table.

Use the field _stageid_value (lookup to processstage) to link the two tables.

Create Relationship:

In Power BI Model view, relate:

opportunity._stageid_value → processstage.processstageid

Use processstage.name:

In your visuals, use processstage.name to display the Pipeline Phase (StepName).

Pipeline Phase (StepName) is not directly stored in the opportunity table as text — it's a lookup (stageid) to processstage.
FetchXML shows it because it resolves the lookup automatically; Power BI needs it joined explicitly.

Was this reply helpful? Yes No
CU09051923-0 13 on at

Like (0)

Report

Importing managed solution Dynamics Dataverse into PowerBI does not display the pipeline phase

Hello Muhammad,

I tried implementing your method.

However, the process stage table and stage ID in Opportunity table are deprecated now in dynamics it seems. As a work around I created a copy of pipeline phase column in the Opportunity table. After publishing this change to production env, I am now able to see the user pipeline phase column (populated) in PowerBI.

I do want to say nonetheless that your method is more elegant and should be used for other such challenges.

I am also interested in hearing if my current implementation may be not well thought off and whether it can cause problems in the future.

Best,

Vickey.

Was this reply helpful? Yes No