I'm running into the same issue after installing Power BI Report Server version 1.2.6660.39920 (Build 220.127.116.119) released March 28, 2018.
We have an expression that uses the MultiLookup function to filter the data in a matrix. When the report is run on the March 2018 version of Power BI Report Server it returns the following error: Failed to evaluate the FilterExpression of the Tablix ‘tblxName’. (rsFilterEvaluationError). However, the report runs fine on the October 2017 version of Power BI Report Server and in Visual Studio.
@frankvanzuilen we plan to put out a CU release which will only have bug fixes and no new features in the next week or so. For new features that have come online in the Power BI service those will get rolled into the next feature release of PBIRS which should be sometime around July.
@mgmeyer Thank for yoour feedback. Please let us know when this CU will be (is) actually available. I assume that this bug (breaking existing LOOKUP functionality) will be solved as well. BR Frank
I noticed that there is a new version of the March update available on the Report Server download page.
It looks like it was released on Saturday. Has anyone tried it yet?
@jbud55 thank you for notifying the community
@mgmeyer the https://docs.microsoft.com/en-us/power-bi/report-server/changelog doesn't show the details yet about this version. Does this new version solve all bugs/issues, or are there still any open items left?
The changelog should be updated soon but to answer your question yes this build addresses the nested Lookup function expression errors as well as several other bug fixes.
I just wanted to confirm that the latest build:
Version 1.2.6690.34729 (Build 18.104.22.1682)
Does indeed fix the issues we were having. At this point, we are going to be moving this to our produciton instances, as it has passed all of our internal regressions.
Ben, we were having the same problem and Build 22.214.171.1242 update resolved it.
May I ask how you found out an update was available for this?
A few posts above this, @mgmeyer posted that a fix would be posted shortly that addressed this issue:
Then @jbud55 posted that he saw the update was made available: