You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 'There is no data for the field at position N.'
The previous version of the report viewer in .NET Framework tolerated that, now having this constraint really does not help in porting hundreds of reports to .NET 5.0. Make it tolerable for not provided dataset fields, make a property with which we can make it tolerable for such issues.
The text was updated successfully, but these errors were encountered:
hovek
changed the title
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 'There is no data for the field at position 2.'
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 'There is no data for the field at position N.'
Jan 26, 2021
Can you post full stack trace where exactly ReportProcessingException it thrown? From my experiments, it should be caught right away in MappingDataReader.GetFieldValue and converted to report warning while producing empty value and continuing report rendering.
Perhaps you get ReportProcessingException as first-chance exception only while debugger is attached?
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 'There is no data for the field at position N.'
The previous version of the report viewer in .NET Framework tolerated that, now having this constraint really does not help in porting hundreds of reports to .NET 5.0. Make it tolerable for not provided dataset fields, make a property with which we can make it tolerable for such issues.
The text was updated successfully, but these errors were encountered: