We use WebServiceDataSource with OData query in our reports. Sometimes OData can through an exception.
In our case, we have added Web Service DataSource and set this OData query for its Service Url:
If you see the query, it is selecting "ProductName1" property of "Product #1". But "ProductName1" property does not exist (correct property name is "ProductName"). When we use Postman for the OData query above, it shows an error which you can see from attached picture (ErrorWhenWeUsePostman.PNG, "Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'"). From the second picture (TelerikReportingGeneralError.PNG, "An error has occurred... Response status code does not indicate success: 400 (Bad Request).") you can see the result of our test report (in html5 report viewer) that has the same OData query.
The question is when we preview our report (in html5 report viewer) how can we show the error message that OData sent instead of showing Telerik reporting general error?
Instead of this message:
An error has occurred while processing Report 'TestReportWithWebServiceDataSource': Response status code does not indicate success: 400 (Bad Request).
This OData error message should be handled and shown on browser (html5 report viewer) when previewing report:
Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'
FYI: We are using Telerik Reporting version 188.8.131.52.
This is my post on Telerik forum related with this: How to get internal error message from Custom Report Resolver
When trying to duplex print a report that has odd page numbers, the next report's first page prints on the back of the previous report. We need the ability to conditionally insert a page break based on whether the report's (the group's) page count is odd or even. Since we don't have access to the global pagecount variable outside the footer, there is no way to use it to insert a page break into the body of the report. This seems like it would be such a common need with the desire by many to save paper that it would be an obvious feature to include in the product. Thanks.
If a table-based item (Table, List, Crosstab) does not fit in a single page and needs to occupy more than one page, its bottom border is not drawn on the first page and its top border is not drawn on the second (subsequent) page. This behavior is by design and its purpose is to help the users visually distinguish the table as a single item. The table has only one top and bottom border and they are displayed at the beginning and at the end of the table, regardless how many pages the table actually occupies.
Since users might find this confusing, a table should have a property controlling this behavior. The default state of the property will preserve the current rendering. If the user explicitly sets the property, then the table will draw its top and bottom borders on every page it occupies.