Forum Discussion

ahmedshalabyy12's avatar
11 months ago
Solved

Field Parameter appear as count

Hello ,

I am using Field Parametet of measures like Sum - Count - Avg , The FP is working the semantic Model .. but when

i try to create a live report from this semantic model the FP appear as count 

 

 

What's the reason for that

Thank you 

7 Replies

  • It's solved FP Don't work with mixed storage 
    Live only working fine 

    Thank you all 

    • ahmedshalabyy12's avatar
      ahmedshalabyy12
      Helper V

      It's working in the semantic Model and tested , but not working in the live report ( data source is the semantic Model ) 

      • FarhanJeelani's avatar
        FarhanJeelani
        Super User

        Hi ahmedshalabyy12 ,

        this is most likely due to field parameters not being supported with a live connection to a semantic model (SSAS/Analysis Services). When you use a live connection, Power BI can’t evaluate the dynamic field parameter the same way as in an imported dataset, so the visual ends up showing a default aggregation like Count.

         

        What you can try or consider:

        If possible, switch to an imported Power BI dataset (or publish a Power BI dataset) instead of using a live SSAS connection. Field parameters work in that scenario.


        If you must stay with a live semantic model, field parameters are not reliable for dynamic measure switching. In that case you have two workarounds:


        Implement the dynamic measure logic on the server side (in the semantic model) using pre-defined measures and a slicer (DISCONNECTED parameter table) that maps to those measures. Note: this requires you to modify the semantic model itself.


        Use separate measures in the report (Sum, Avg, Count) and provide a manual way to switch visuals via bookmarks or a slicer, but this won’t be a true field parameter switch in real-time.

         

        Check the datatype of the field parameter column in the semantic model. A mismatch (e.g., numeric vs text) can cause odd behavior. If you can, ensure the parameter column is a text/string type and that the parameter table is properly designed for a field parameter.

         

        Please mark this post as solution if it helps you. Appreciate Kudos.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi ahmedshalabyy12,

     

    Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to FarhanJeelani and ChiragGarg2512  for prompt and helpful responses.

     

    Please consider marking your reply on 6/6 as the accepted solution so it can help other community members facing the same issue.

     

    Thanks & Regards,

    Prasanna Kumar