Marco AntonioniAugust 16, 2016 at 2:02 am #2442
a couple of questions about behaviour of “Data Export” widget and its compatibility with “Service Data Table”.
See attached pdf.
Thanks in advance.
Marco.SPARK SupportAugust 16, 2016 at 9:21 am #2445
After discussing these items with development, we have identified the failure to export all data due to table pagination as a bug and will address the defect in an upcoming release. As for the lack of column names when binding the export to a variable, this was by design at the time to prevent confusion between exporting the column names of the table and the variable names of the bound data. We may consider using the variable names as the column names in the export in an upcoming release.
Stephen P.Marco AntonioniAugust 17, 2016 at 7:22 am #2446
Thanks a lot Stephen.
The second question was about the “Service Data Table”, is this control supported by Data Export ?SPARK SupportAugust 17, 2016 at 5:13 pm #2452
Support for the Service Data Table with the Data Export control is planned in an upcoming release.
Stephen P.Prashant TiwariDecember 8, 2016 at 11:26 am #3256
Is the support for Service data table available yet ?
I tried to export xls from a Service Data table using Export widget, it creates a file but does not have any data in it.SPARK SupportDecember 8, 2016 at 5:14 pm #3260
This issue is still in our backlog as it has a low priority since the Export functionality does work for the Table control.
Stephen P.Stuart JonesJanuary 4, 2017 at 6:59 pm #3433
I just upgraded to SPARK UI 446CE, hoping to get a fix for using the Data Export control with a paginated table. However, when I generate the .xlsx file, I find that I still only get the first page of data. I saw in the release notes for 4.4.4, the statement “Fixed issue with Data Export control and table data”. I don’t know if this refers to the issue with pagination so I’d like to know if this is supposed to be fixed in 446 or if it is another issue that’s fixed in 444?
If this is supposed to be fixed, can you suggest what I might have done wrong?
Thanks, Stuart JonesSPARK SupportJanuary 5, 2017 at 5:35 pm #3448
The issue fixed in version 4.4.6 for the Data Export control corrected a reference error when the Table or Data Export control were placed in certain containers.
The Data Export control can be bound to the same variable as the table, and will export all rows even when paged.
Stephen P.Stuart JonesJanuary 5, 2017 at 8:22 pm #3449
Thanks for getting back to me. I didn’t see any documentation about binding the Data Export to the same variable as the target Table – this probably needs to be added somewhere. So, I altered my Data Export, binding it to the same variable as my table. When I click on the Data Export button, I get an exception. If I clear the binding of the Data Export control, it works but only gives me the first page of data.
I included a couple of screenshots. The first shows my Coach with the paginated table, the second shows the exception in my Chrome Console Log. Please let me know if there’s something that I should be doing differently or if this is still not working.
Thanks, Stuart…SPARK SupportJanuary 6, 2017 at 3:54 pm #3452
I have reproduced this issue. There appears to be a bug when exporting a complex variable type.
This bug has been logged and will be fixed in an upcoming release.
Thank you for the feedback.
Stephen P.SPARK SupportFebruary 21, 2017 at 2:08 pm #3789
After looking more into the issue you experienced, we have observed that you can use the Data Export control to export a Complex object type, as long as that Complex object does not have nested Complex data objects. Excel would not be able to display these sub-sets of data. In your example, what is the data structure of the object that you are trying to export?
Elliot P.Maniraj ChandrasekarDecember 23, 2018 at 4:44 am #5374
Is there any solution or workaround to export as excel functionality for paginated Table ? In my list BO, i have many column apart from table data. So if i export the bind variable, i am getting many unwanted columns. It would be great, if i get any solution for this. Thanks!!SPARK SupportDecember 24, 2018 at 7:19 am #5375
The Data Export control will either export all rows displayed in a Table that are not paged, or export all columns and all rows contained in a bound variable. There is no option to control which columns will be exported from the bound variable.
You can try to work around this issue by starting your table to fully load all rows, and then set the Page Size in the On Load event of the Table. This way, the paged data will already be loaded on export.
Otherwise, feel free to submit a Request For Enhancement to IBM here : https://www.ibm.com/developerworks/rfe/?PROD_ID=546
You must be logged in to reply to this topic.