Unplanned
Last Updated: 17 Nov 2023 14:11 by ADMIN
Scheduled for 2024 R2
NPL IT
Created on: 18 Oct 2023 19:46
Type: Feature Request
2
"Unable to get report parameters" incorrectly stated as the reason a report won't display.

When a system tells users they should look into the report parameters as the reason the report isn't displaying.  It's reasonable for your users to believe you aren't misleading them. 

The report viewer error message misleads users.  In reality the parameters are correctly configured and it the repot URL could be wrong.  Or a variety of other issues are at play; for instance, a problem with you connection string will also return the "Unable to get report parameters" error message.  I'd like to see this error message at minimum changed to "report can't display."   It's better to throw out a generic message vs having users spend hours or days troubleshooting the report parameters.  Better yet a proper catch/validation system put into place please.  

1 comment
ADMIN
Todor
Posted on: 25 Oct 2023 09:51

Hello Drew,

Thank you for this input. I agree that there are misleading messages displayed by our viewers.

Indeed, the Error Unable to Get Report Parameters is usually due to the report not being resolved. The request to Get Report Parameters is made by the viewer so that it may display them in the Parameters area. This requires the report to be resolved and when this fails server-side the error message comes from the failing request.

The error message displays 'Report reportName.trdp/x cannot be resolved.' as well. This may be clarified further, for example with hints that the report file cannot be found on the path, etc., so that the user is not misled that something is wrong with the parameters.

Regards,
Todor
Progress Telerik

Stay tuned by visiting our roadmap and feedback portal pages, enjoy a smooth take-off with our Getting Started resources, or visit the free self-paced technical training at https://learn.telerik.com/.