Page 2 of 3
Re: Problem with databand on report with differing page margins
Posted: Tue Mar 23, 2021 12:25 pm
by Lech Kulikowski
Hello,
We need some additional time to investigate the issue, we will let you know about the result.
Thank you.
Re: Problem with databand on report with differing page margins
Posted: Wed Mar 24, 2021 7:24 pm
by Lech Kulikowski
Hello,
In last versions, in NetCore, the compilation is working, and compilation is enabled in the report. During compilation, events from the base report are not transferred, so it does not work.
There are two options here.
- or turn on the interpretation mode so it's the same as before. in the designer for this particular report, or in the code after loading the report:
report.CalculationMode = StiCalculationMode.Interpretation;
- or write this code directly in the report event script.
We advise interpretation because it is faster and consumes less memory.
Thank you.
Re: Problem with databand on report with differing page margins
Posted: Thu Mar 25, 2021 7:03 am
by n.froeh
Hello,
well thank you for your help for that problem. The described solution works well.
Now we can come back to the problem described in post:
n.froeh wrote: ↑Thu Mar 11, 2021 11:13 am
Hello,
thank you for your help with the last issue we had.
We have one more problem with dynamic page margins and the rendering event.
We use the viewer controller with the dynamic page margin like in the previous example with a bigger left and right margin (see ViewerController.cs).
We have a report with a databand with different fields, some are docking to the right (field3), some are docking to the left (field1) and one big field is filling the remaining space in the middle of the databand (field2). (see Report PdfCutOffIssue.mrt with data PdfCutOffIssue.json)
The problem is that the
exported pdf cuts off the text of our "field2", although it is displayed correctly in the viewer.
The text is displayed correctly in the viewer:
DesignerCorrect.PNG
The last line is missing in the exported pdf:
PDFIncorrect.PNG
I tested some things and found out, that the problem relies on the dynamic page margins and the dock styles, but could not find a solution.
Is there a fix for this issue?
Thank you for your help and i'm looking forward to an answer.
With the reports and the attached viewercontroller you should now be able to reproduce my actual problem (different output when using dynamic page margins in pdf and viewer for some fields).
Is there a fix for this issue?
Thank you for your help.
Re: Problem with databand on report with differing page margins
Posted: Mon Mar 29, 2021 6:21 am
by Lech Kulikowski
Hello,
We need some additional time to investigate the issue, we will let you know about the result.
Thank you.
Re: Problem with databand on report with differing page margins
Posted: Tue May 04, 2021 5:41 am
by n.froeh
Hello,
is there an update on this issue?
Thank you for your help.
Re: Problem with databand on report with differing page margins
Posted: Tue May 04, 2021 7:26 am
by Lech Kulikowski
Hello,
We couldn't reproduce the issue.
Please send us a sample project that reproduces the issue for analysis.
Thank you.
Re: Problem with databand on report with differing page margins
Posted: Tue May 11, 2021 8:54 am
by n.froeh
Hello,
i attached the sample project (
). It's the basic show report in the viewer example with a different ViewerController (dynamic page margins) and report.
As described the text of field 2 is cut off if exported as pdf (it is displayed correctly in the viewer).
I'm looking forward for an answer. Thank you.
Re: Problem with databand on report with differing page margins
Posted: Fri May 14, 2021 8:07 am
by Lech Kulikowski
Hello,
We are working on the problem. We will let you know when the solution is available.
Thank you.
#4074
Re: Problem with databand on report with differing page margins
Posted: Tue Jun 01, 2021 5:49 am
by n.froeh
Hello,
is there an update on this?
Greetings
Re: Problem with databand on report with differing page margins
Posted: Tue Jun 01, 2021 9:09 pm
by Lech Kulikowski
Hello,
We are working on the problem. We will let you know when the solution is available.
Thank you.