Why does the query change on its own when I add a field?

[GoingIncognito]

Hi.

As a data model for my file I use XMLA connection to the portal. My paginated report returns the right values, as in same values as in desktop file, up to the point where I add Calendar[date]-field to the paginated reports dataset. Then the query changes FROM:

EVALUATE SUMMARIZECOLUMNS(RSCustomDaxFilter(@PortfolioPORID,EqualToCondition,[Portfolio].[PORID],String),

TO: EVALUATE SUMMARIZECOLUMNS('Kalenteri'[Date], RSCustomDaxFilter(@PortfolioPORID,EqualToCondition,[Portfolio].[PORID],String),

The latter one is wrong. Otherwise the queries are the same. Why does this happen? Is it because I use the Calendar[date] also as a parameter? When I want to use it also as a field in my visual elements on the report should I just write it by hand to the query after FILTER() ends and imported fields are stated, e.g.: "Revenue", Sum(money), "Calendar date", Calendar[date] ... ?

Thank you.

[d_gosbell]

---

@GoingIncognito wrote:

The latter one is wrong. Otherwise the queries are the same. Why does this happen?

---

Why are you saying this is wrong? If you have added the date to the data set the query will need to include the data field.

Any columns you add to the dataset will get injected into the start of the SUMMARIZECOLUMNS function, then any parameters will get injected as filters and finally any measures will be inserted.

If you add the date to the dataset as both an output column and a parameter I would expect to see it appear in the query as both a column and in a FILTER expression.

Can you explain in more detail what you mean by the second query being "wrong" ?

[GoingIncognito]

You're right - it's the right thing to happen. And yes it should obvious from the get-go.

But what I don't understand is, when I add a field like Calendar[Date], or Customer[Name] the measures return odd values. And this was what I was wondering, when I went so confused that I asked the above question. Which makes no sense, because like you said. That's what is supposed to happen.

Silly me. 😄

[d_gosbell]

---

@GoingIncognito wrote:

But what I don't understand is, when I add a field like Calendar[Date], or Customer[Name] the measures return odd values.

---

So that's a different question 🙂 and depends on what the expression is in your measure and what your data model looks like in terms of the relationships between the tables. We would need the sort of information suggested in the following post to be able to answer this sort of question - https://community.powerbi.com/t5/Community-Blog/How-to-Get-Your-Question-Answered-Quickly/ba-p/38490

[GoingIncognito]

The point I should have originally made, or to be more exact the question I'd have originally made, is how come the report works just fine in PBI desktop. But when I use that file as a data source in paginated report some of the measures return odd values. The reports are identical.

So the answer has something to do with the query paginated report produces? And there's no way of adding certain columns without the measure breaking. I'm so confused I don't know where to begin?

[d_gosbell · Accepted solution]

---

@GoingIncognito wrote:

So the answer has something to do with the query paginated report produces? And there's no way of adding certain columns without the measure breaking. I'm so confused I don't know where to begin?

---

without being able to see the queries, measures and data model it's impossible to answer this question. If you can provide a specific example with information as suggested in the follow: https://community.powerbi.com/t5/Community-Blog/How-to-Get-Your-Question-Answered-Quickly/ba-p/38490 we should be able to explain the issue you are seeing