Forum Discussion

fcoalcantarajr's avatar
fcoalcantarajr
Frequent Visitor
3 years ago
Solved

PowerBI CycleTimeDays average and Azure DevOps Cycle Time widget does not return me the same number

Hi y'all. I have been trying to build a panel using PowerBi that includes the CycleTimeDays average for a project. I've followed this tutorial step-by-step: Lead time and Cycle time sample Power BI report - Azure DevOps | Microsoft Learn 

 

But it still diverged from the number shown the Cycle Time widget, which is this one:

The value I get by following the tutorial is this one:

Can someone help me?

Here's the PBIX file, if it helps: Sample panel.pbix - Google Drive

 

  • Anonymous's avatar
    Anonymous
    3 years ago

    HI fcoalcantarajr,

    I mean if the line chart and card visual get the same result, it means the expression should worked and equally to the default aggregation effect. The difference results may due to the underlying data source records changes.

    Regards,

    Xiaoxin Sheng

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi fcoalcantarajr,

    Where did the first result geted? I check your sample file and find the both two card get the same result.(one of aggregated on table fields, the other is measure formula)

    If you mean the sample file result, you may need to check the report data source if they not static. The expression result is based on row context, and it may not get the same result if the underlying data records changes.
    Regards,

    Xiaoxin Sheng

    • fcoalcantarajr's avatar
      fcoalcantarajr
      Frequent Visitor

      Hi Anonymous 

      I didn't quite get your message, sorry. =(

      But yes, the data is not static, it keeps changing. The source is a Feed OData connection with Azure Boards.

      • Anonymous's avatar
        Anonymous
        Not applicable

        HI fcoalcantarajr,

        I mean if the line chart and card visual get the same result, it means the expression should worked and equally to the default aggregation effect. The difference results may due to the underlying data source records changes.

        Regards,

        Xiaoxin Sheng