Report generation, max size

Hi all.
I'm working on a pressure and temp system acquisition. I'm saving the data every 5 sec in a database, then i have 17280 data in 1 day. ¿Can I run a report (Report Generation Tool) directly from the database showing data trends from a entire week? (120960 points) The trends (graphics) are not importants in 1 day and that's the reason because i need to process one week. How can do this??
Thanks and BR.
Saludos.

Hi,
Yes, it's possible to do it, and we have a lot of examples inside LabVIEW, here is attached one of them where you can create graphs in Excel using the Report Generation Tool.
If you have any problems using it, please inform us.
Thiago Matos
Engenharia de Aplicações
National Instruments Brasil
Attachments:
Bar Graph Excel.vi ‏27 KB

Similar Messages

Report Generation excel column size

Dear,
In the project, I save the data in Excel with Report Generation. I would like change just the column size of my Excel report. There is an explanation in the labview help but I have always an error when I run the VI.
I work with labview 8.2
A VI is joined with a simple example.
Regard
Julien
Attachments:
report table graph.vi ‏21 KB

Julien,
I realize you only want to modify columns, but you need to put in a start and stop row value other than -1. Try setting the start and stop rows to 0.

Changing the Size of generated graph in excel report generation toolkit

Hi, i am trying to build a report generation vi for my Structural health monitoring system in which i need to export 3 graphs in to an excel report. The idea is to have the report on a single page, but when i paste them along with the ceiling and pillar deviation percentages, the report just exceeds the page limit. I wanted to know whether one can change the size of the graphs in excel? One can do it in word(tried that), but i dont want to use the bookmark option as it intend to put this up as a webservice in the next step. I am using LabVIEW 2009 Thanks.
LabVIEW 8.2,8.6,2009...still learning
Attachments:
Report Generation SHM.vi ‏30 KB

Hi,
I haven't tried this myself, but looking through the report generation toolkit the "Excel format image VI" (in the Excel specific tab of the Report Genertaion window) looks to be the one you are after. The help entry for the VI says to: "Use this VI to format any type of image in a worksheet, including front panel images, images from a file, and graphs"
Hopefully this will help.
-CC
"If anyone needs me, I'll be in the Angry Dome!"

Report Generation Toolkit missing VI

LabVIEW version 8.6.1
Report Generation Toolkit 1.13
I have just started work on an ongoing project that others have been contributing to for some time. (Hence the project being in older versions of LabVIEW)
On my PC, I am apparently missing the VI "Word Get ActiveX References.vi"
I do have the version 1.13 of the toolkit installed, just as every other machine that runs this code does. But my word.llb does not contain that VI
I have tried simply copying that VI into the .llb The VI is then found by the application. But is not executable due to this error: This VI is connected with a library that does not include the VI. The VI might have been deleted from the library. Add the VI to the library again or select File»Disconnect from Library.
I have also tried replacing my entire C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\addons\_office\ directory with files from a PC that was working. Again, I get the same error as above.
I did attempt to do a repair on my installation of the toolkit. But as far as I can tell, this didn't do anything.
I also tried simply reinstalling the toolkit. But since it was already installed, it did nothing. I am hesitant to uninstall and reinstall the toolkit for fear of breaking all of my 8.6 projects, as well as possibly my 2009 projects. I wouldn't think it mess with my 2009 installation. But I do know that the order in which things are installed can be critical in system with multiple versions. I'm not sure if this applies to toolkits or not.
This PC also has an installation of LV 2009 SP1, and that version also has the Report Generation Toolkit installed. (although it is a different revision of the toolkit than 1.13)
I know that in the past, multiple versions of this toolkit were not compatible, meaning only one installed version of LabVIEW could have a working Report Generation Toolkit installed. But I was of the understanding that this was no longer a problem. Although it may not be a coincidence that neither of the other development boxes running this code do not have LV 2009 installed.
Has anyone else ever run into a similar problem and found a solution?
Thanks.
Patrick Allen
Solved!
Go to Solution.

Darren wrote:
Back before we unified the LabVIEW and toolkit version numbers (in 2009), there were cases where we didn't change the version number in the registry for one reason or another on a minor upgrade.
Ah. This makes sense then.
I just reinstalled said toolkit from said SSP DVD and although it did tell me that I was about to install 1.1.4, MAX still thinks it's 1.1.3
...except that now I do have the missing VI. This is a good thingTM
I still wonder how it ended up missing, because I'm really sure this is where I installed the toolkit from in the first place. I'll probably never know for sure. But that's a lot easier to take when the code is working.
Thanks!
Message Edited by pallen on 04-15-2010 04:52 PM
Patrick Allen

Report Generation Toolkit Error Quick Question

Hi,
I created the most awesome LabVIEW report ever at my desk using a trial version of the RGT and Office 2003. I took this to my production machine and ")@#(&%(*#^%()^!!!" The production machine has office 2007 and a fully licensed version of the RGT. Both machines have LabVIEW 8.6.0. I've read all the stuff about these errors and something about classes and dll's and whatnot's. So my quick question, is: Instead of matching the versions of Microsoft Office as recommended, can I just rewrite from scratch the VI that creates this world's most awesome LabVIEW report on the production machine to create the same effect?
Solved!
Go to Solution.

Hi
Quick Answer: Probably
Slower answer: Microsoft changed a lot of things behind the scenes in Office 2007, but the Report Generation toolkit version 1.1.3 supports Office 2007 so you should be good to go. Depends on what functions are included in your VI. Liek the read me says "Several default settings in Microsoft Office 2007 differ slightly from previous versions. Reports you generate using Office 2007 might look different than reports you generate from other versions of Office because font sizes, cell sizes, and so on, differ."
Best Regards
David
NISW

-1073741819 code using Report Generation with LV 6.1

I'm studing about the Report Generation Functions with LV 6.1, and I'm trying to run some example about it, but the programs sends the next error: "Error -1073741819 ocurred at unknown System error in Font Style.vi> Set report font.vi>Easy text report.vi
>. I'm using Windows XP plataform.
someone knows what can I do?
Thanks for your help

Maybe you already know this but the font settings is a cluster of 4 elements: 2 integers and 2 strings. The 2 integers are character set and weight. They default to -1. The two strings are font name and font size. The default to blank strings. Are you wiring this cluster into your font settings terminal? Do you have -1, -1, Arial, and a number for font size inside the cluster (I use 4 for HTML reports)?
- tbob
Inventor of the WORM Global

Drill down Error in Report Generation

Hi,
I've a problem with a Report generation.
The ERROR Message is the following one:
Odbc driver returned an error (SQLExecDirectW).
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] Generic error. [nQSError: 27002] near <(>: syntax error [nQSError: 26012] . (HY000)
SQL Issued: {call NQSGetQueryColumnInfo('SELECT "Pivot xTD"."ID Report", "Pivot xTD"."Ordine Raggruppamento 1", "Pivot xTD"."Ordine Raggruppamento 2", "Pivot xTD"."Raggruppamento 1", "Pivot xTD".Valore, "Territorio"."Coda", "Territorio"."UT", DBO.FN_GET_PIVOT_LABEL_BI("Pivot xTD"."Label",TIMESTAMP ''2011-03-28 00:00:00.000'',TIMESTAMP ''2011-03-28 00:00:00.000'',"Calendario"."Max Giorno Pivot (formato data)",''Giornaliero''), EVALUATE(''DBO.FNC_GET_DATE_LABEL_BI(%1,%2,%3,%4)'' AS CHAR(500), TIMESTAMP''2011-03-28 00:00:00'', TIMESTAMP''2011-03-28 00:00:00'', Calendario."Max Giorno Pivot (formato data)", ''Giornaliero''), EVALUATE(''DBO.FN_GET_PIVOT_LABEL_BI(%1,%2,%3,%4,%5)'' AS CHAR(500), "Pivot xTD".Label, TIMESTAMP''2011-03-28 00:00:00'', TIMESTAMP''2011-03-28 00:00:00'', Calendario."Max Giorno Pivot (formato data)", ''Giornaliero''), Territorio.Coda, case "Pivot xTD"."ID KPI" when ''LAVORATO_BO_TOTALE'' THEN ''Totale'' when ''LAVORATO_BO_RECLAMI'' THEN ''di cui Reclami'' when ''LAVORATO_BO_AC'' THEN ''Di cui AC'' when ''LAVORATO_BO_CARTACEO'' THEN ''di cui Cartaceo'' when ''LAVORATO_BO_TELEFONICO'' THEN ''di cui Telefonico'' end FROM "Reportistica Predefinita"')}
SQL Issued: SELECT "Pivot xTD"."ID Report", "Pivot xTD"."Ordine Raggruppamento 1", "Pivot xTD"."Ordine Raggruppamento 2", "Pivot xTD"."Raggruppamento 1", "Pivot xTD".Valore, "Territorio"."Coda", "Territorio"."UT", DBO.FN_GET_PIVOT_LABEL_BI("Pivot xTD"."Label",TIMESTAMP '2011-03-28 00:00:00.000',TIMESTAMP '2011-03-28 00:00:00.000',"Calendario"."Max Giorno Pivot (formato data)",'Giornaliero'), EVALUATE('DBO.FNC_GET_DATE_LABEL_BI(%1,%2,%3,%4)' AS CHAR(500), TIMESTAMP'2011-03-28 00:00:00', TIMESTAMP'2011-03-28 00:00:00', Calendario."Max Giorno Pivot (formato data)", 'Giornaliero'), EVALUATE('DBO.FN_GET_PIVOT_LABEL_BI(%1,%2,%3,%4,%5)' AS CHAR(500), "Pivot xTD".Label, TIMESTAMP'2011-03-28 00:00:00', TIMESTAMP'2011-03-28 00:00:00', Calendario."Max Giorno Pivot (formato data)", 'Giornaliero'), Territorio.Coda, case "Pivot xTD"."ID KPI" when 'LAVORATO_BO_TOTALE' THEN 'Totale' when 'LAVORATO_BO_RECLAMI' THEN 'di cui Reclami' when 'LAVORATO_BO_AC' THEN 'Di cui AC' when 'LAVORATO_BO_CARTACEO' THEN 'di cui Cartaceo' when 'LAVORATO_BO_TELEFONICO' THEN 'di cui Telefonico' end FROM "Reportistica Predefinita"
Can someone help me?
Thanks a lot.
Edited by: user13313458 on 20-mag-2011 2.58
Edited by: user13313458 on 20-mag-2011 3.01
Edited by: user13313458 on 20-mag-2011 3.02
Edited by: user13313458 on 20-mag-2011 3.02
Edited by: user13313458 on 20-mag-2011 3.03
Edited by: user13313458 on 20-mag-2011 3.05

Thanks a lot for your answer.
I tried to run the query in a SQL editor, and i've noticed that there's a function that lost its own parameters:
EVALUATE('DBO.FNC_GET_DATE_LABEL_BI(%1,%2,%3,%4)' AS CHAR(500),
 TIMESTAMP'',
 TIMESTAMP'',
 Calendario."Max Giorno Pivot (formato data)",
So i've tried to rune the function in this way:
EVALUATE('DBO.FNC_GET_DATE_LABEL_BI(%1,%2,%3,%4)' AS CHAR(500),
 TIMESTAMP '2011-01-01 00:00:00.000',
 TIMESTAMP '2011-01-01 00:00:00.000',
 TIMESTAMP '2011-01-01 00:00:00.000',
 'string')
but the error is the same.
What can i do?
Edited by: user13313458 on 23-mag-2011 3.02

Report Generation broken after deployment - Excel Set Cell Color and Border.vi

Upon deployment, the Excel Set Cell Color and Border.vi became broken. After installing LV2010 SP1 to view the VIs in the deployment, I noticed that in the second case structure where the code draws the border using the BorderAround invoke node, there is an extra variant input parameter named 'Parameters'. Upon right-clicking, an option to 'Relink Invoke Node' appeared and after selecting this, the extra input disappeared and the VI was no longer broken.
Why does "Relink Invoke Node" appear? How do I create a deployment with this issue? Has anybody else experienced this? Why is the TestStand deployment so buggy?

Hi Ching-Hwa,
I have set up a test deployment here where I am deploying a workspace that contains a sequence file. This sequence file has a LabVIEW Action Step calling a VI that opens a new Excel file and simply calls the Excel Set Cell Color and Border VI. After deploying this, both the VI and my test sequence ran on the deployment machine without error. Therefore, I do have some more questions to more accurately reproduce what you are seeing.
First, what operating systems are you developing on and deploying to? Also, what license do you have for TestStand on the machine you are deploying to? If you have a development version, can you manually take the sequence file and VI to this machine and run it? I know you now have LabVIEW 2010 SP1 on your development machine, but if you have the development version of TestStand as well, it would be interesting to see if you copy the files over if you still see this behavior. Are you including the TestStand Engine in the deployment?
Can you open a blank VI on the deployment machine and add the Excel Set Cell Color and Border VI? It would also be interesting to see if this is not a product of the deployment, but rather an issue with something on the deployment machine itself. What version of the Report Generation Toolkit do you have on each machine? Also, what versions of Excel are you using on the development and deployment machine? Again, it would be helpful for me to know exactly what versions you have installed on both the development and deployment machines so that I can reproduce this as accurately as possible.
One last thing to try, too, would be to try deploying the VI by itself just to see if it also has the same behavior. Do you have the Application Builder in LabVIEW? If so, could you also try building an executable from the VI, create an installer, and deploy this to the deployment machine?
In regards to the "freezing" of code by removing the block diagrams, I do not believe this will be a proper work around in this case. While this removes the block diagram from actually being deployed along with the VI and restricts users from editing the code on the deployment machine, if something is getting changed in the compiled code upon deployment, this will not stop this from happening. This option is available more as a memory option to lower the size of the deployment as well as prohibit any users on the development machine from editing the block diagram themselves.
Thanks, Ching-Hwa! I look forward to your response so that I can continue trying to reproduce this issue. Have a great day!
Taylor G.
Product Support Engineer
National Instruments
www.ni.com/support

Report generation Footers

Greetings all... hope someone can help.
I inherited a huge Labview application that works well. I have been tasked with cleaning it up and adding some info to the report. The report uses the Report Generation Vi's including New Report, Append Image to Report, Set Report Font, etc... New Report is set to Word type. Report Generation Toolkit is installed. I am trying to add a footer to the report. I can do that easily enough, however, it seems like the footer is limited to 2" in length. As a result, the last 5 characters of the footer wraps to the next line. It does not matter whether I select left, center, or right. The footer is 25 characters long, and the font size is 12 (standard). The system is running Word 2007. I can't for the life of me figure out how to get the footer to accept a longer text string.
I have attached an image of the section of code in question. pls... be nice lol As I said, I inherited this and not much planning was done as to how the report would look at the time. You will see a string constant comprised of a number sequence going into the footer report vi. This is for testing only and allows me to see easily how many characters it will accept.
can anyone help??????
Attachments:
labview image.jpg ‏238 KB

Hi Franco,
Much like when you write a document in Word, there is just a set limit to the amount of text you can fit across one line of the page. Much like you can in Microsoft Word when editing yourself, you can use the Set Report Margins VI to set the margins to be smaller so that more text will fit on the page. Apart from making the text's font smaller, this is one of the few solutions to fitting more text per line. Thanks!
Stephen Meserve
National Instruments

Report generation toolkit: Avoid a separation of title and image at pagebreak in a work document.

I want to generate a report with the report generation toolkit in LV7.1.
In that report I use several report VIs to append text, titles and frontpanel images to a word document template (Office 2003). That works fine.
Depending on the size and text of my generated report, I have sometimes a problem with pagebreaks: A image is set to a new page if there is not enough space to place it on the old one. That’s ok. The text/title above the image is still on the old page. That's right, but I don’t want this. I know in Word you can use the paragraph formatting options to avoid a separation. But with the corresponding VI from the toolkit (word format paragraph (adv)) it seems not to work. With this VI you should have access to "indents and spacing" and to "line and page breaks". I always and only can change the "indents and spacing". En- or Disabling line or page breaks with this VI does not work, nothing changes in a word document.
Has anyone some suggestions or other solutions?
Thanks in advance!

Thanks for your input. You are right, that works and could be an alternative.
In the meantime I found a solution with creating my own activex vi instead of that from the toolkit as you can see in the attached image. Maybe this could help someone with similar problems...
Attachments:
KeepWithNext.JPG ‏46 KB

Report Generation Toolkit Table Row Height-MS Word

I am having trouble setting the table row height in the report generation toolkit. I can set the column width fine, but the row height seems to remain the same no matter what I set it to. I have attached the VI that generates and formats the table, and the printout it is resulting in. I have also attached the template file I am using.
Any tips to get this to work right? I am trying to make the cells exactly the same height as the text inside.
Solved!
Go to Solution.
Attachments:
AddMarkersToReport.vi ‏20 KB
badFormatting.pdf ‏179 KB
splitter.docx ‏13 KB

Hi,
So I tried .2 and it didn't work. So I went to Word to manually change it, and it did not work either. There is a selection box in word, for the table properties, that seems to default to the value "at least". When I changed this manually to "exactly" in word, no problem with the .2 manually in Word.
Hopefully this can be set within the template, for all new inserted tables. I'm not sure the report generator VI's expose this property. Well, this is a start for the issue.
Edit ****
You can go into the add table VI and expose the property. See pic. However, you have to decide if you want to "upgrade" this VI permanently to expose this property or make a copy with the property exposed. I haven't messed with the new class reports too much, so not sure of the ins and outs with this.
I think this is the issue with the row size becoming smaller.
Mark Ramsdale

Excel report generation

Hello,
I am looking for a simple solution to this simple problem:
I have generated an excel data file using LabVIEW Report Generation Toolkit for Microsoft Office ( see diagram below ).
Now I would like to add data to this worksheet every time I run this VI ( data must expand in column format instead of
row) but i have no Idea how to do it .
I would appreciate any help.
Thanks
Attachments:
Excel Report.jpg ‏59 KB

That's what the start input is for. You tell it where to insert the cells.
Asides:
Why aren't you wiring the error out from the new report function to the next function?
Do not autoindex an array and wire a value to N. Do one or the other, not both. If you do both the loop will run for whichever value (N, or the array size) is smaller.
Your loop with the function node can be simplified by replacing it with a single Divide function and feeding the Divide function the arrays directly. The numeric functions (as well as many other functions) are polymorphic.
To learn more about LabVIEW it is recommended that you go through the introduction material, tutorial(s), and other material in the NI Developer Zone's Learning Center which provides links to other materials and other tutorials. You can also take the online courses for free.

Setting the title font and axis labels in a graph created with the Report Generation Toolkit

I'm using the LabVIEW Report Generation Toolkit for Microsoft Office to generate Excel worksheets containing plots. Unfortunately, the default font size used in the plots is huge (see attached worksheet). I was able to use Excel Set Graph Font.vi to reduce the size of the axis labels, but there does not appear to be a function to do this to the title and legend. In addition, there does not appear to be a function to set the axis text labels. Before I write my own, has NI released additional functions to perform these tasks?
Thanks for your help,
Zach Lerner
Software Engineer
OnWafer Technologies, Inc.
Attachments:
Test1_-_embedded_graph's_title_and_legend_font_is_huge.xls ‏14 KB

Hello Zeidan
The graph title and legend font sizes can be changed by accessing a low level VI (Excel_Insert_Chart.vi) that is part of the excelsub.llb that is located at (C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\addons\_office). This VI is called dynamically from within the Excel Insert Graph.vi and it uses VI server technology to access the Excel exposed properties. Attached to this post is an image of the block diagram of this VI after I have modified it to set the font sizes of the title and legend to 15. The circles in the image represent what I had to add to accomplish this.
Best Regards,
Ayman Kabire
Attachments:
Excel_Insert_Chart.JPG ‏99 KB

Report Generation MS Word Table Bug

Hi everybody,
I am using Word 2010 and LV2010 and I am unable create a proper table with Word using the Report Generation Toolkit. Excel and HTML work fine, but Word fails. Not even the Examples work as they are supposed to.
When using the attached VI (see screenshot below)
the result appears as follows:
Temperature
Temperature
Temperature
Temperature
Temperature
Data 1
Data 1
Data 1
Data 1
Data 1
Data 2
Data 2
Data 2
Data 2
Data 2
Does anyone have an idea?
Thanks in advance.
ben
Solved!
Go to Solution.
Attachments:
test_table.vi ‏10 KB

OK, if NI won't provide a workaround, I'll create my own:
The problem stems from the fact that the NI Report Toolkit populate a Word table by first creating an empty table of the correct size, then placing the table contents into the copy buffer, then selects the whole table and uses Paste to push the data into the table. The problem is actually in Word, because in Word 2010 it interprets the contents of the copy buffer differently.
The solution is to alter the data that gets pushed into the copy buffer by the NI Report Toolkit. To implement my fix, you will need to alter one VI of the NI Report Toolkit (so you might want to make a backup in case this stops it from working in other previous release of Word).
Open [LabVIEW installation folder]\vi.lib\addons\_office\_wordsub.llb\Word_Insert_Table.vi
There is a nested for loop that interprets the provided string array data and reformats it into a long ASCII string for the copy buffer. It should look like this:
Change the nested loop to look like this:
The changes I've made are twofold:
1. Within the inner loop, replace the "\n" char with a Tab character
2. Just after the inner loop, add a new "concatenate strings" function that adds "\n".
This alters the string that the toolkit places into the copy buffer. You should find that report tables now populate correctly in Word 2010!
This is untested on previous releases of Word, and could possible introduce problems there, so if anyone could test this for me it would be most appreciated
Best of luck!
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Dynamic crystal report generation - issues with column headings

Hi All, 
I'm trying to generate a crystal report dynamically based on a "result set" data(Query: select REPORT_ID, REPORT_NAME, REPORT_DESC, RPT_FILE_NAME, LOCATION from IRS_REPORT_DETAILS). I'm able to generate the report run time, But the report is without columns heads. I would like to include the column headings as well. 
I searched the API(RAS) and found that there is a 'add(java.lang.String fieldName, java.lang.String headingText) " method present in "ReportObjectController" using which we can add the headings. 
ReportDefController reportDefController = clientDoc.getReportDefController();
ReportObjectController reportObjectController = reportDefController.getReportObjectController();
reportObjectController.add( "{Table.Field}", "FieldName" );
 
I'm facing problems in using this code. When trying to use this function for my fields(Ex: reportObjectController.add( "{ IRS_REPORT_DETAILS.REPORT_ID}", "Report ID" );) it is giving me the following error: "com.crystaldecisions.sdk.occa.report.lib.ReportSDKGroupException: The field was not found.---- Error code:-2147213310 Error code name:fieldNotFound" 
The following is my dynamic crystal report generation code: 
public ReportClientDocument execute(String repName, String query) {
 ReportClientDocument boReportClientDocument = null;
 try {
 boReportClientDocument = new ReportClientDocument();
 boReportClientDocument.newDocument();
 // Add a table based on the given Resultset to the report.
 dbConnResultSet mySampleResultSet = new dbConnResultSet();
 //mySampleResultSet.execute(query);
 boReportClientDocument.getDatabaseController().addDataSource(
 mySampleResultSet.execute(query));
 IReportSource test = boReportClientDocument.getReportSource();
 // Access all the database fields
 DatabaseController databaseController = boReportClientDocument
 .getDatabaseController();
 IDatabase database = databaseController.getDatabase();
 Tables tables = database.getTables();
 ITable table = (Table) tables.getTable(0);
 int NO_OF_FIELDS = table.getDataFields().size();
 int LEFT_POSITION = 200;
 // Add all the database fields to the report document
 for (int i = 0; i < NO_OF_FIELDS; i++) {
 IField field = table.getDataFields().getField(i);
 FieldObject fieldObject = new FieldObject();
 fieldObject.setFieldValueType(field.getType());
 fieldObject.setDataSource(field.getFormulaForm());
 IReportObject rep = (IReportObject) fieldObject;
 IObjectFormat objformat = rep.getFormat();
 objformat.setEnableCanGrow(true);
 objformat.setHorizontalAlignment(Alignment.from_int(1));
 rep.setFormat(objformat);
 rep.setLeft(LEFT_POSITION);
 rep.setWidth(1000);
 LEFT_POSITION = LEFT_POSITION + 1000 + 50;
 ISection section = boReportClientDocument
 .getReportDefController().getReportDefinition()
 .getDetailArea().getSections().getSection(0);
 //***************** Data being added to the report here, But headings are not added*****************
 boReportClientDocument.getReportDefController()
 .getReportObjectController().add(rep, section, i);
 boReportClientDocument.createReport();
 /*Some report saving code is present down*/
 } catch (ReportSDKException ex) {
 ex.printStackTrace();
 } catch (Exception ex) {
 ex.printStackTrace();
 return boReportClientDocument;
 
appreciate your help.

IField field = table.getDataFields().getField(i);
Here you are getting the first field in the array. This may not be the field you want to add since we aren't sure how the arrays are ordered when retrieving fields from the report. It is better to retrieve the fields with the findObjectByName method, thus ensuring you are retrieving the field you want to add to your heading.

Report generation, max size

Similar Messages

Maybe you are looking for