Stimulsoft Business Intelligence System | Forum

Hello,
in the past you have solved a problem with the crosstab which is described
in the under lines. I was very glad, when I saw the result of your fix about
the Rowheader-problem in spring this year (build 2018.2.2).
Now I would update our program with build 2018.2.3 and unfortunately
I saw a new problem in the CrossTab.
A Field in the Crosstab doesn't grow anymore. In the picture below you see
the problem.

The field which doesn't work


The CrossTab field grow in version 2017.2.2


The CrossTab field doesn't grow in version 2018.2.2 and version 2018.2.3

****************************************************************************************************
The requestnumber was 3151152.

Hello,
we have a problem wir Cross-Tab.
If the report has more columns than space on one page, then a second page
is automatically printed.
There the Rowheader is not displayed correctly.
In the first picture, the row-headlines are fine. This is the first page.
In the second picture you see the wrong rowheaders.
In the past it worked fine. When the error occurred I can not say.
Currently we use the version Stimulsoft.Reports.Wpf 2017.2.2.0
Thank you!
Best regards

Hello,

Please send us a sample report with test data which reproduces the issue for analysis.

Thank you.

Hello,
in the attachement you find a small project with solutionfile.
First, you have to copy Stimulsoft-Libraries version 2018.2.3 to
the directory Libraries.
Then, please build the project and check the report with the program.
There you see the no-growing of the column "Ansatz". The current
version of the Stimulsoft-Libraries is 2018.2.3.
Now change the Stimulsoft-Libraries to version 2017.2.2 and the
field grows well.
Thank you.

Hello,

We need some additional time to investigate the issue.

Thank you.

Hallo,
when is it planned to fix this issue?
Thank you

Hello,

We need some additional time to add this fix in the WPF.

Thank you.

Hello,
is this issue fixed?
Thank you.

Hello,
I have tested the new version 2019.2.1 today,
and I found the bug is fixed.
Thank you
and best regards

Hello

We are always glad to help you!
Please let us know if you need any additional help.

Thank you.