Add remarks for REMOVEFILTERS #350
Conversation
Explaining behavior for column arguments
|
@cwebe135 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 737cc96: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
|
||
| - If multiple columns are specified, they must be from the same column. | ||
|
|
||
| - If a single solumn is specified, and the target column is sorted by another column, both columns must be included as arguments. This is because DAX includes both columns in the underlying query, so the inclusion of the sort by column adds the filters back in, as described in [this article](https://www.sqlbi.com/blog/marco/2018/05/04/removing-column-filter-in-power-bi-when-sort-by-column-is-active/) on :::no-loc text="sql.bi.com":::. |
There was a problem hiding this comment.
not a fan of links to sqlbi. We should document this ourselves.
There was a problem hiding this comment.
Agreed. That article refers specifically to ALL. Should I add a synopsis to the ALL page and refer to it here, or explain the behavior in both places?
There was a problem hiding this comment.
@jeroenterheerdt Should the adjustments to documentation ("we should document this ourselves") be done now or in a later PR?
There was a problem hiding this comment.
I won't accept links to SQLBI in our documentation. So it has to be documented in this PR.
3 participants
Explaining behavior for column arguments