One of the big problems we always have is that different users want to see different part of the data and they hate to filter and slice it every single time. Only other workaround is to create a sep...
One thing is add possibility to save my filter/slice for next refresh ... great idea! Second one is ability to have in data some parameter about logged (effective) user and use it for default filter/slice. For example when we have nice report for sales team, it would be great immediately to see for every user revenue from “my” customers, my stock value, data of my subordinates etc. Now user must always and always filter “his data” or we have to create dozen similar report for every single user.
Recent ideas
executeDaxQueries-like API call with effectiveUserName on SSO-enabled model with Service Principal
Please provide a way for a service principal to execute DAX - with an effective user name - against an SSO-enabled directlake semantic model and get per-user results that respect lakehouse OneLake Se...
