Forum Discussion
Power BI Embedded visual fails with HTTP 403 when using custom DAX measures
- 1 year ago
Hi mpatino123 ,
Even if a table is hidden or not directly visible in a report, Power BI still requires it to be listed in the effectiveIdentity. tables array if a DAX measure refers to it, whether directly, through a relationship, or via another measure. If it’s missing, your visual will show a 403 error.
1. Use tools like DAX Studio or Tabular Editor to check which tables your measures depend on.
2. Ensure the embed token includes every referenced table, even hidden ones or those in filtered relationships.
3. It's not about what's visible on screen it’s about whether the token recognizes the table.
Key points to remember.
1. Hidden tables or columns must be included in the embed token if your DAX measures use them.
2. If a required table is missing from the embed token, Power BI won’t explain the error properly. it will just throw a generic 403 error, which usually means data access was denied, not a calculation mistake.
Thank you for your response tharunkumarRTK .
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
Referencing invisible columns in dax might not be the problem in this case.
Have you added all the end users to the security role? If yes, for the user who were facing this issue, ask them to open the report URL, if they were able to reder the report properly in power bi service then this is not an issue with RLS but issue is with the way of embedding. If not then its an issue with RLS.
Using test as role in desktop wont give you clarity on where the issue is
Need a Power BI Consultation? Hire me on Upwork
Connect on LinkedIn
|