use of Integer Data Item in Report

mkpjsr

Hi all,

I have seen Integer data item in most of the navision Reports. I want to know ---

1. How one should use integer data item.
2. what is the impact of indenting one Integer Data Item under another Integer Data Item as so on.

3. How to control repeatation of content on Integer Data Item, is SETRANGE(Number,1,UserDefinedNumber) enough for it

kine

Just search the forum. There are enough posts about this subject.

David_Singleton

Or better...

why not just look at the code in these reports and see what they are doing and why. if you need tutorials and hand holding, speak with your senior who will organize training for you.

mkpjsr

Actually I want to print multiple copies of Excise Invoice (Id: 16593) Report, so I am trying to do this as It has been done in report Sales Invoice (id:206) and I am writing the following code under IntegerHeader - OnPreDataItem()

NoOfLoops := ABS(NoOfCopies) ;
IF NoOfLoops <= 0 THEN
NoOfLoops := 1;
CopyText := Text100;
SETRANGE(Number,1,NoOfLoops);

and under IntegerHeader - OnAfterGetRecord()


IF Number =2 THEN
CopyText := Text200;
IF Number =3 THEN
CopyText := Text300;
IF Number =4 THEN
CopyText := Text400;

but the report is showing only the first page...

kine

Ad how you are setting the NoOfCopies?

mkpjsr

kine wrote:

Ad how you are setting the NoOfCopies?

I am taking it as input from request form.

ssingla

The printing is controlled by MaxIteration property of the dataitem "IntegerHeader".

mkpjsr

ssingla wrote:

The printing is controlled by MaxIteration property of the dataitem "IntegerHeader".

If i am changing MaxIteration property to 4 then other Integer Sections are not printing properly,
Interger (1) Header and body is printing at the bottom. Only the first page is perfectly printed and rest three pages are disturbed.

ssingla

Write the following code on trigger "On After Get Record" of IntegerHeader dataitem.

IF CurrReport.PAGENO<>1 THEN
  CurrReport.NEWPAGE;

mkpjsr

ssingla wrote:

Write the following code on trigger "On After Get Record" of IntegerHeader dataitem.

IF CurrReport.PAGENO<>1 THEN
  CurrReport.NEWPAGE;

Thanx for the reply,
still, the second page's sections are not displayed properly. Rest three pages, page 1,3 and 4 is perfect. what is the reason

ssingla

It is working properly here. The only thing needed was to initialize certain variables but format is correct. Check whether you have made some other changes to the report?

mkpjsr

ssingla wrote:

The only thing needed was to initialize certain variables but format is correct. Check whether you have made some other changes to the report?

I have not made any changes in the code,still i am facing the same problem.

If we look at the report 206 (Sales-Invoice) it has CopyLoop and PageLoop Integer data items.
And in this report code is written under CopyLoop and the report is designed in PageLoop data item section's. why they are using two Integer data items, is not one Integer DataItem sufficient for that? As in excise invoice report there is IntegerHaeder on which we are doing the whole or I should use Integer1 data item also.

mkpjsr

can anybody guide me??

geronimo

mkpjsr wrote:

ssingla wrote:

The only thing needed was to initialize certain variables but format is correct. Check whether you have made some other changes to the report?

I have not made any changes in the code,still i am facing the same problem.

If we look at the report 206 (Sales-Invoice) it has CopyLoop and PageLoop Integer data items.
And in this report code is written under CopyLoop and the report is designed in PageLoop data item section's. why they are using two Integer data items, is not one Integer DataItem sufficient for that? As in excise invoice report there is IntegerHaeder on which we are doing the whole or I should use Integer1 data item also.

the reason there are 2 integer loops is:
- copyloop to iterate the total number of copies
- pageloop to set the format correctly (for the pages with the header sections) as you cant use an integer as a top level for a document as you cant pass a record along to the report in a standard way (like report.runmodal(50000,Rec)

if the design of page 2 is faulty then this means some sections are printed too much or not printed. just look at what the reason is some sections arent printed (maybe adding in a caption box with a number in the sections and previewing the report to see what is missing or too much will be the fastest way)

navuser1

geronimo wrote:

if the design of page 2 is faulty then this means some sections are printed too much or not printed. just look at what the reason is some sections arent printed (maybe adding in a caption box with a number in the sections and previewing the report to see what is missing or too much will be the fastest way)

I have made the changes as required in the Classic client (R2 version) and It's working fine. But it Prints Extra page( Page No 2, Without any data) in RDLC Report Output..

What could be the cause :-k :-k ??
Kindly Reply..

Sog

Why do you ask the same question when you have a topic open in 3-tier?
My rule of thumb with rdlc reports with pages being printed too much is to check the dataset being sent to the rdlc report to see if the problem is datawise (too much data being sent) or layoutwise (a missing or misplaced check if data should be printed or not, needed for totalling lines.)