12 votes5 comments · Power BI Ideas » Gateways (Enterprise and Personal) · Flag idea as inappropriate… · Admin →
I believe you can do this by modifying the gateway config file per this posting:
Here are the steps to change this configuration:
On the gateway machine, open the file: [Program Files]\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config
Find the “MashupDefaultPoolContainerMaxCount” setting.
Change its value to the desired value.
Save and restart the gateway.
Changing this property value to 1 means that all queries will run sequentially, which could be desired for specific data sources that don’t support or don’t perform well with concurrent requests.
This would help us too. Because Oracle does not support uncommitted reads parallel queries against the same database can create a big performance hit related to "latch: cache buffers chains".
Thanks for all the feedback on this! We are definitely planning on adding Incremental refresh to Pro. Do know though that it is a fair amount of work, so it may be a bit before we can give you a more firm timeline.
In the meantime, keep voting so you’re notified when we do have more information to share!
You could create or add a whole dimension to existing visualizations, very exciting.
The relative date slicer (a Preview feature as of June ‘17) gets us close to this with the ’This Month’ or ‘This Year’ settings. That is a dynamic date selection that updates based on the current system date. We plan to add a ‘YTD’/‘MTD’ option to specifically select a range from the start of the month/year up to today, hopefully that’ll address the remaining requirements!
Also, the comments below do not address what Brian is trying to do. Power BI RLS is post query, not at query time. Also the solution offered by anonymous to "=Sql.Database("(localdb)\v11.0","",[Query="SELECT SYSTEM_USER"])
should do it" will not work as most queries, particularly if going through a gateway will have the service account context not the user running the report.
We very much need this. This would allow us to provide security and context for many of our visuals. The role based RLS is not scalable when you have thousands of employees also the RLS data already lives in our database we just need to pass it the current user to retrieve data they are authorized to see. Another issue is often this data is sources from transactional finance tables with millions of rows. Pulling down the whole table then applying Power BI RLS after the fact is often again not practical.
Let me break down what happens and what I think “should” happen…
Scenario: We make a super cool dashboard in Power BI and share it with the university president, sending him an email with a link to the dashboard.
What I think should happen:
President clicks on link
Dashboard loads in his browser*
*Possible authentication prompt of not already authenticated in O365, in a properly configured SSO environment no prompts at all.
President clicks link
President is prompted to sign-up for Power BI or “click here” to sign in
President accidently attempts to sign up for Power BI or president clicks sign-in and has to re-authenticate with Power BI even though already logged into O365
President wonders why I make things more difficult than they need to be
President sees awesome dashboard and forgets “a few extra clicks and login”
Note: This only happens the first time someone visits app.powerbi.com, on subsequent there is no prompt for sign-up.
Assumptions: user is authenticated with O365, user has a valid Power BI Pro license
Hopefully this illustrated what we are experiencing and the experience we are shooting for.Lyle Spencer shared this idea ·
Thanks for voting, everyone. We’re actively considered this and more votes will move it up our backlog.
We are looking to improve our maps. A new Shape Map control is expected in the summer which will solve some of these issues.
628 votesunder review · 28 comments · Power BI Ideas » Administration · Flag idea as inappropriate… · Admin →