Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
3 years ago
Solved

PowerBi dataflow return NA in refresh history report

Hi,

I wonder why I get NA values for several fileds in datafloe regresh history report.

I would like to have number of rows added and total byte size for each refresh.

Refresh status for each refresh requested was completed without any errors and warnings.

Please have a look the screenshot from the report.

 

Thank you!

 

 

dataflow
  • Anonymous's avatar
    Anonymous
    3 years ago

    Thank you for your reply.

    I enabled enhanced computing but it is still NA for rows processed even tough there is no long durations. 

    Could it be that it does now show beacuse of premium trial?

3 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    3 years ago

    Hi Anonymous ,

    Premium refreshes provide more information based on the extra compute and dataflows capabilities, versus Pro based dataflows that reside on shared capacity. As such, some of the refresh metrics are available only in Premium.

     

    For more details, you can read related document: Understand and optimize dataflows refresh - Power BI | Microsoft Learn

     

    Best regards,
    Community Support Team_Binbin Yu
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • Anonymous's avatar
      Anonymous
      Not applicable
      3 years ago

      Thank you for your reply.

      I enabled enhanced computing but it is still NA for rows processed even tough there is no long durations. 

      Could it be that it does now show beacuse of premium trial?

      • ikavaju's avatar
        ikavaju
        Frequent Visitor
        3 years ago

        Hi,

        I have similar issue. I am using "Diamond" workspace with premium capacity. 

        My dataflow whhich I am trying to refresh is linked table reference and then I have only filters in the dataflow. And when I refresh, I get no errors, but "Rows processed: NA". I haven't encountred this issue before this week. I feel this case was not `yet solved in this thread.

         

         

        Any idea how to resolve this?