![]() By default, 8.97 and subsequent releases will have only one page header. There are individual page header nodes nested under the PageHeaders node, one for each page of the report where a reprint page header was explicitly called by the report logic. This is an example of the page header information that is included in the XML output for a batch version of the Purchase Order Print report: You should design the page headers and page footers in the BI Publisher template. ![]() This ensures that the headers and footers do not break up the report data.ĭesign your reports in RDA without including page headers and page footers. ![]() Information that is contained in page headers and page footers of RDA reports is grouped together at the top of the XML output. Each piece of data is enclosed within descriptive item tags that include the object ID. When the node of a section is expanded, you can view the item tags of the individual records. The, , and nodes are all conditional sections that are called by the level break footer. The level break footer information is at the same level as the level break header information because both level break sections break on the same field. The information that resides directly under the node is level break footer information. The page header number indicates where the data resides in the RDA report. This is an example of an individual section that is included in the XML output for a batch version of the Purchase Order Print report: The object ID is retrieved from the report specifications and cannot be modified. The object ID is assigned by RDA to ensure that each report object is unique. The object ID begins with the letters ID to indicate that it is a field from the report. An exception to this rule is that if the data dictionary name has been overridden in RDA, then the override is used as the item tag.īecause multiple data items in an RDA report template can be named the same, the item tag in the XML output is appended with an object ID. Item tags that you see in the XML output are determined by the data dictionary name of the fields used in the RDA report template. The fourth node is a section that groups all associated level break headers and level break footers with the report detail section. This node appears only when the batch version includes columnar sections. The second node is the Column Headings Language node. The first node under the report template name is the Properties node. All other nodes are nested under this report template node: The first node of the XML output displays the name of the Purchase Order Print report template, R43500. This is an example of the sections that are included in the XML output for a batch version of the Purchase Order Print report: The section ID is retrieved from the report specifications and cannot be modified. The section ID is assigned by RDA to ensure that each report section is unique. The section ID begins with the letter S to indicate that it is a section from the report. The name that you see in the XML output is the same as the name found in the Description field of the Section Properties form.īecause multiple sections in an RDA report template can be named the same, the section tag in the XML output is appended with a section ID. Section tags are determined by the name that is specified in JD Edwards EnterpriseOne Report Design Aid (RDA).
0 Comments
Leave a Reply. |