Planned
Last Updated: 17 Nov 2021 14:35 by Kori
Scheduled for R1 2022

At the moment it's only possible to have your reports in old-fashioned projects.

It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).

Planned
Last Updated: 05 Mar 2021 12:53 by ADMIN
Scheduled for R3 2021
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.
Planned
Last Updated: 11 Dec 2020 10:48 by ADMIN
Scheduled for R2 2021
Add progress bar that indicates when the report would be fully rendered.
Planned
Last Updated: 28 Oct 2020 19:02 by ADMIN
Scheduled for R1 2021

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.

Planned
Last Updated: 25 Jun 2020 15:06 by ADMIN
The MsSqlServerStorage class uses a hard-coded string "TR" for its ApplicationName attribute in the connection string. This hard-coded string should be configurable and should not overwrite already existing ApplicationName attribute, if set.