Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi everyone,
My organization currently use Power BI Pro and I am a main person who creates reports for them. However with a growing dataset of my my company, I am currently facing error when do scheduled refresh with error timeout: 7200s. I've read and know that the Pro account only support 7200s while Premium support 18000s so I switch my account to Premium (only my account) and the issue has been fixed. Unfortunately, my teammates cant see the report anymore and I see that they must change their license type to Premium also. So is there another way to fix this error without upgrade all my organzation accounts (cost saving).
Thank you so much.
Solved! Go to Solution.
Hey @aibikaidau ,
unfortunately there is no way, regarding licensing, if an artifact is created with Premium Per User then all users require a Premium Per User licensing.
You can consider using aggregation tables and incremental refresh to stay with Pro licensing. Keep in mind that that aggregation tables are basically direct query models no matter if some tableś, the aggregation tables, are imported. This means that your measures must be optimized for direct query and it very likely that you will face a slow down of responsiveness of your reports.
Hopefully, this adds some idea and helps to tackle your challenge.
Regards,
Tom
Yah, sad to hear that there is no way. Well now I must to explain to my organization and recommend them to upgrade. Btw, thank you so much for your help :).
Hey @aibikaidau ,
unfortunately there is no way, regarding licensing, if an artifact is created with Premium Per User then all users require a Premium Per User licensing.
You can consider using aggregation tables and incremental refresh to stay with Pro licensing. Keep in mind that that aggregation tables are basically direct query models no matter if some tableś, the aggregation tables, are imported. This means that your measures must be optimized for direct query and it very likely that you will face a slow down of responsiveness of your reports.
Hopefully, this adds some idea and helps to tackle your challenge.
Regards,
Tom
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
49 | |
32 | |
27 | |
27 | |
27 |
User | Count |
---|---|
61 | |
56 | |
34 | |
29 | |
28 |