Forum Discussion
Query string reference problem
- 2 years ago
Hi ronrsnfld ,
As far as I'm aware, the intrinsic variables (#sections, #shared) can only be used within PQ when using PBI Desktop and not passed to the model. My assumption is, because they are environmental keywords i.e. they give information about the current environment, and the data model can't give that environmental info, this is what breaks it.
Why it seems to work in PQ for Excel I have no idea.
You could possibly try @'ing Ehren into this thread if you need the technicals on it.
Pete
- 2 years ago
For perf reasons, in PBIDesktop refresh, we trim any queries that aren't being referenced (directly or indirectly) from the mashup document and replace them with a null value. References by name via #sections or #shared don't count, so they get turned into null.
Hi ronrsnfld ,
As far as I'm aware, the intrinsic variables (#sections, #shared) can only be used within PQ when using PBI Desktop and not passed to the model. My assumption is, because they are environmental keywords i.e. they give information about the current environment, and the data model can't give that environmental info, this is what breaks it.
Why it seems to work in PQ for Excel I have no idea.
You could possibly try @'ing Ehren into this thread if you need the technicals on it.
Pete
- Ehren2 years agoMicrosoft Employee
For perf reasons, in PBIDesktop refresh, we trim any queries that aren't being referenced (directly or indirectly) from the mashup document and replace them with a null value. References by name via #sections or #shared don't count, so they get turned into null.