Hi all,
If you haven't read the part first then read it here.
Now when you created the suggestion layout you can see the Red Dots in the Report body. For being specific in the table details of the first table in the Page Body.
The most part of an RTC Report is the Page Header, we all face issues in this.
Let's discuss what happens when we say suggest layout.
Check the Expression for each text box in the Page Header.
you will find something like =ReportItems!VendAddr_1_.Value.
How does it get value for this parameter during run time?
If you check it in details you will find that one of the Red Dots in the Page Body have same name and same value.
During run time it computes value from the Red Dot and populates the same.
Issues If we Use the Standard Layout -
If you haven't read the part first then read it here.
Now when you created the suggestion layout you can see the Red Dots in the Report body. For being specific in the table details of the first table in the Page Body.
The most part of an RTC Report is the Page Header, we all face issues in this.
Let's discuss what happens when we say suggest layout.
Check the Expression for each text box in the Page Header.
you will find something like =ReportItems!VendAddr_1_.Value.
How does it get value for this parameter during run time?
If you check it in details you will find that one of the Red Dots in the Page Body have same name and same value.
During run time it computes value from the Red Dot and populates the same.
Issues If we Use the Standard Layout -
- You cannot set the visibility property for the table detail row. (will discuss it on later post)
- You might find blank spaces in the report while printed.
- Page header might not be printed in all the pages, in case where report get printed in multiple pages.
- It extends the size of the report Body, as the number of Red Dots consumes one column.
Comments
Post a Comment