1. Home
  2. Forum
  3. jQuery
  4. Lookup cause rendering to fail
Starting in 2019, the Reporting control is no longer included in Essential Studio®. If you're experiencing issues with the Syncfusion� Reporting Platform, Report Viewer, Report Designer, or Report Writer, we recommend migrating to Bold Reports, our dedicated reporting platform.

Bold Reports offers a comprehensive suite of tools and features for all your reporting needs, and we will help you make a smooth transition from the discontinued control. Our support team at https://support.boldreports.com/ is here to assist you with any questions or difficulties you may encounter during the migration process.

We thank you for choosing Syncfusion� and appreciate your understanding.

Lookup cause rendering to fail

Hi.

We have started to use report viewer component. And testing some reports that we used to have in SSRS repository.

While testing, we have observed an error message when a report has Lookup expression in anywhere.

I am sharing two RDL files in the attachment for you to reproduce it. 

LookupTest_1: in this RDL, as lookup expression, I used always Fields!<<FieldName>>.Value syntax. In this case, reports return rendering exception.

LookupTest_2: in this RDL, as lookup expression, I used always ReportItems!<<ReportItem>>.Value syntax. In this case, reports Lookup function returns an incorrect value.

Please check following screenshots.

I am looking forward to seeing your assessment on this.
Regards



Attachment: LookupTest_RDLs_45431bf7.zip

5 Replies
MS Mahendran Shanmugam Syncfusion Team May 30, 2018 01:26 PM UTC

Hi Osman, 
 
Thanks for contacting Syncfusion support, 
 
LookupTest_1: in this RDL, as lookup expression, I used always Fields!<<FieldName>>.Value syntax. In this case, reports return rendering exception. 
We have already fixed the mentioned problem at our end. The fix will be included in our Essential Studio Volume 2 main release which is estimated to available on next week. 
LookupTest_2: in this RDL, as lookup expression, I used always ReportItems!<<ReportItem>>.Value syntax. In this case, reports Lookup function returns an incorrect value. 
We are able to reproduce the mentioned problem at our end. We have confirmed that the issue is a defect and logged a defect report on this. The fix for the issue is estimated to be available on our upcoming Essential Studio Volume 2 sp1 release. 
 
 
Regards, 
Mahendran S. 


OS Osman June 1, 2018 08:46 PM UTC

Thanks for the update. Will be looking for next releases then. Hopefully, they get released as planned in next week.

Regards 

MS Mahendran Shanmugam Syncfusion Team June 4, 2018 04:28 AM UTC

Hi Osman,  
 
Thanks for the update. As updated the fix changes will be included in our upcoming release. 
 
Regards, 
Mahendran S. 


OS Osman replied to Mahendran Shanmugam June 11, 2018 08:51 PM UTC

Hi Osman, 
 
Thanks for contacting Syncfusion support, 
 
LookupTest_1: in this RDL, as lookup expression, I used always Fields!<<FieldName>>.Value syntax. In this case, reports return rendering exception. 
We have already fixed the mentioned problem at our end. The fix will be included in our Essential Studio Volume 2 main release which is estimated to available on next week. 
LookupTest_2: in this RDL, as lookup expression, I used always ReportItems!<<ReportItem>>.Value syntax. In this case, reports Lookup function returns an incorrect value. 
We are able to reproduce the mentioned problem at our end. We have confirmed that the issue is a defect and logged a defect report on this. The fix for the issue is estimated to be available on our upcoming Essential Studio Volume 2 sp1 release. 
 
 
Regards, 
Mahendran S. 


Hi 

Has timeline changed for Essential Studio Volume 2 release? It was expected to be released last week

YD Yuvaraj Devarajan Syncfusion Team June 12, 2018 09:33 AM UTC

Hi Osman, 

We are having some delay in our side due to the priority issues in license enforcement changes. You can expect the release on next week. 

Regards, 
Yuvaraj D. 


Loader.
Up arrow icon