Forum Discussion

Wresen's avatar
Wresen
Post Patron
1 year ago
Solved

Direct Query Subscriptions comes out blank

Hi and thx for reading this.   I have a report that uses 2 direct querys. It is 3 sheets (pages). if you do a subscriptions to the report (in the top of the report little to the left of middle ...
Need Help
  • V-yubandi-msft's avatar
    V-yubandi-msft
    1 year ago

    Hi Wresen ,

    1. Use Power BI's built in slicer instead it’s fully supported in both Desktop and Service environments.

    2. If you need the advanced features of the Attribute Slicer, explore AppSource for certified custom visuals with similar capabilities. Certified visuals are tested for reliability, compatibility, and subscription support.

    For further information, please refer to Microsoft's official guidance on subscriptions and visual limitations: FAQs about Troubleshoot subscribing to dashboards and reports - Power BI | Microsoft Learn

     

    Best regards,
    Yugandhar.

Akash_Varuna's avatar
Akash_Varuna
Super User
1 year ago

Hi Wresen  It might be because Power BI subscriptions struggle to capture visuals accurately when slicer changes impact DirectQuery performance or query timing. Ensure the underlying queries are optimized, simplify visuals, and test slicer interactions in Power BI Service. Save the report with the desired slicer settings and republish to align with the subscription. If the issue still exists consider exporting static snapshots or increasing query timeouts for better performance.

Wresen's avatar
Wresen
Post Patron
1 year ago

Thanks Akash_Varuna 
The subscriptions is not for me but for others and they might have diffrent "settings" in the slicers from each other so i am not sure that saving it will work.
Yeah it will take 20-40 sec to excecute the change in the report with slicers (its alot of calculations)
I have the querr set to "no limit" in Pbi desktop, not sure if that is the "increasing query timeouts for better performance".
/Thanks

  • Akash_Varuna's avatar
    Akash_Varuna
    Super User
    1 year ago

    Hi Wresen The long slicer execution time (20–40 seconds) likely exceeds Power BI Service's limits. Check the dataset's query timeout settings in the Service. For varying slicer settings, use PDFs or Paginated Reports for consistent results.

    • Wresen's avatar
      Wresen
      Post Patron
      1 year ago

      Thanks Akash_Varuna 

      Where do i check this "dataset's query timeout settings in the Service" ??

       

      Just to clearify(bad explaination from me)  , the slicers does not take 20-40 sec, they are instant , the graphs takes 20-40 secs after the slicers are set 🙂

      (the slicers uses importerad data and are used as parameters for the 2 direct querys)

      • V-yubandi-msft's avatar
        V-yubandi-msft
        Community Support
        1 year ago

        Hi Wresen ,

        Regarding query timeout settings in Power BI Service, there isn’t a direct UI option to configure them per report. However, timeouts are influenced by

        1. The data source own timeout settings .
        2. On premises data gateway configurations, if applicable.
        3. Power BI Service limits, including a visual query timeout of 225 seconds.

        A few ideas to improve reliability:

        Simplify visuals or split the report into smaller pages to reduce load times. If users need different slicer settings consistently, consider.

        1. Paginated Reports, which handle subscriptions and large datasets more efficiently.
        2. Exporting static PDFs, pre filtered as needed for each user.

        For more detailed guidance on optimizing DirectQuery performance, you can refer to the official Microsoft documentation: DirectQuery in Power BI - Power BI | Microsoft Learn

         

        Regards,

        Yugandhar.