cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
BenMackin Frequent Visitor
Frequent Visitor

PBRS March Update breaking existing RDL reports that use LOOKUP function

It looks like something in the March update for Power BI Report Server is causing a breaking issue on RDL/SSRS reports that utilize the Lookup function (or it's derivatives LookupSet or MultiLookup).

 

For example, I have a column defined as:

 

=SUM(Fields!Loan_Balance.Value) / Lookup(Fields!Year_and_Month_and_Group.Value,Fields!Year_and_Month_and_Group.Value,Fields!Customer_Count.Value,"ReportDetails_Summary")

 

In the October release of PowerBI Report server, this works just fine, and returns the values I would expect. Also in Visual Studio 2015 with SSDT 14.0.61712.050, the report will preview just fine.

 

However, when I deploy this report to an upgraded server running the March release of Power BI Report Server, the column just returns with an "#Error". I can't seem to find anything in the log file that shws why this is an error. If I remove the SUM component, and just use the lookup, I get back a value. But for some reason the combination of the two functions doesn't work on the latest version.

2 ACCEPTED SOLUTIONS

Accepted Solutions
Power BI Team mgmeyer
Power BI Team

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

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.

View solution in original post

BenMackin Frequent Visitor
Frequent Visitor

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

I just wanted to confirm that the latest build:

 

Version 1.2.6690.34729 (Build 15.0.2.402)

 

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.

View solution in original post

30 REPLIES 30
Power BI Team mgmeyer
Power BI Team

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

Thanks for reporting the issue this is something we are looking into. One question for you, are you using the Lookup function in the Header/Footer of the report or is it on the main canvas? How many reports do you have that are impacted by this? We do have one possible work, you can create a report level variable that contains the Lookup function and then reference that in your nested expression.

BenMackin Frequent Visitor
Frequent Visitor

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function


@mgmeyerwrote:

Thanks for reporting the issue this is something we are looking into. One question for you, are you using the Lookup function in the Header/Footer of the report or is it on the main canvas? How many reports do you have that are impacted by this? We do have one possible work, you can create a report level variable that contains the Lookup function and then reference that in your nested expression.



The lookup function is in the tablix on the main canvas.

 

Capture.PNG

 

In total, we have 10 reports that are impacted.

 

As for the variable, I don't think that solution will work. Right now, we have the lookup being using in a column on a tablix. So it is repeated for each row. If I try and use a variable, I get the following error:

 

The Variable(LookUpTest1) expression for the report 'body' refers diorectly to the field 'Year_and_Month_and_Group' without specifing a dataset aggregate. When the report contains multiple datasets, field references outside of a data region must be contained within aggregate functions which specify a dataset scope.

 

In my case I don't think I can perfrom any aggregates, as the data is row level.

BenMackin Frequent Visitor
Frequent Visitor

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

@mgmeyer, it looks like there are some more bugs we have identified with the RDL/Paginated reports in this latest March update of Power BI Report Server

 

When we use an aggregate function in a page footer, we get an #Error message on the new version. On the old October version this worked fine.

 

Code example:

 

="Market(s): " + IIF(Parameters!P_MA.Count = Sum(Fields!ParameterLevel.Value, "P_MA_Param"), "All", Join(Parameters!P_MA.Label, ", "))

 

We were able to work around using a variable:

 

="Market(s): " + IIF(Parameters!P_MA.Count = Variables!MarketAll.Value, "All", Join(Parameters!P_MA.Label, ", "))

 

But if we need to update all reports for this bug, it becomes an issue. Were there some regressions that got missed when building this new release? Looking at the change log, there isn't a lot of changes to the RDL/Paginated reports, so it is surprising to find so many breaking issues.

Power BI Team mgmeyer
Power BI Team

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

Thanks Ben for the update, we are actively looking into the issue and hope to have a fix soon. To your question around changes there we changes that do impact RDL reports however most of the them were infrastructure related.

BenMackin Frequent Visitor
Frequent Visitor

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

Awesome.

If there are any log files, or stack trace files, that I can send let me know. More than willing to help out troubleshoot.
frankvanzuilen Frequent Visitor
Frequent Visitor

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

Is this a general issue. In other words: the "Lookup" functions don't work at all in this PBRIS March 2018 release.

My customer has some 15 reports using this kind of functionality.

BenMackin Frequent Visitor
Frequent Visitor

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

Hard to say.

 

I have many reports that use lookup. Some of them have no issues. Some of them have issues. I can't exactly tell what causes the #Error, but it seems like if the lookup is used in conjunction with anything else, it fails.

 

Best thing I can say to do is test it out. Install the update on a test instance, and load up your RDL files. Initialy, our plan was to spot check reports, since it didn't seem like there was any real changes around RDL reports in this release. But seeing as how we have found these breaking issues, we are going through the process of evaluating all 180 reports we have on our system.

frankvanzuilen Frequent Visitor
Frequent Visitor

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

@BenMackin Thank you for your feedback. We used the "Lookup" function to display the data in conjuction with other data sources data, and used in the sorting of the tables/matrices as well. Both sorting and display caused issues in all our reports.

 

@mgmeyer We decided to rollback to the October 2017 version, which wasn't a simple uninstall of the March version, and a re-install of the October version. It seemed that the "ReportServer" database scheme was changed as well by the "March version" because the PBIRS/SSRS service couldn't connect to the "ReportServer" database anymore. After a restore of the "ReportServer" database with a back-up just before the upgrade everything was working again.

- Could you confirm that the "March version" indeed applied some changes to the "ReportServer" database scheme.

- When will a patch be available for the reported issues so far?

 

BR Frank

Highlighted
frankvanzuilen Frequent Visitor
Frequent Visitor

Re: PBRS March Update breaking existing RDL reports that use LOOKUP function

@mgmeyer I noticed that a new patch/build was released for the PBIRS "March Version".

However the changelog doesn't mention that this bug/issue has been fixed as well. Could you verify whether this bug/issue was also (unmentioned) fixed in the latest patch, or that it will be fixed in another patch?

 

Version 1.2.6660.39920 (Build 15.0.2.389), Released: March 28, 2018

  • Bug fixes
    • For Power BI Reports (PBIX), fix for Export Data not working from Power BI Visuals
    • For Power BI Reports (PBIX), fix for URL filters not working
    • For Paginated Reports (RDL), fix for images not being displayed correctly in IE11 after upgrading to Power BI Report Server March release

Helpful resources

Announcements
Ask Amanda Anything Q&A

Ask Amanda Anything Q&A

Learn the answers to some of the questions asked during the Amanda Triple A event.

October 2019 Community Highlights

October 2019 Community Highlights

October was a busy month in the community. Read the recap article to learn about some of the events and content.

New Solution Badges

New Solution Badges

Two waves of brand new solution badges are coming! Read the article for more information on our new community badges.

Analytics in Azure virtual event

Analytics in Azure virtual event

Experience a limitless analytics service built to ingest, prep, manage, and serve data for immediate use in Power BI.

Top Kudoed Authors
Users Online
Currently online: 480 members 4,558 guests
Please welcome our newest community members: