Hello,

Over the past several weeks and months, I had several interactions with IBM support on issues around exporting and importing data and elements, all in PAW.

Meaning that, an export does not happen, or it gives a CSV file with only the header line (dimension names). Or the export takes place but the import of that same file in the same cube on development does not finish. Sometimes the data is prepared but the file is not downloaded. Etc.

This topic is just to let you know that a number of these tickets lead to known defects and IBM are correcting them. First have a look at known defects before spending too much time or creating new support tickets.

Hi Wim,

The CSV export feature that we added is generating an MDX query and pushing the results of that query to a file.  One possible reason why a valid MDX query might fail is the MaximumViewSize parameter in TM1 being set too low.  We are working on some improvements to detect when the query failed and properly indicate the failure to the user.

We are still working on functionality in PAW books that will allow action buttons to be used to run a TI process and download the results.  The significant difference between using MDX and TI processes to export is model security (TI processes ignore security). 

Hello,

Over the past several weeks and months, I had several interactions with IBM support on issues around exporting and importing data and elements, all in PAW.

Meaning that, an export does not happen, or it gives a CSV file with only the header line (dimension names). Or the export takes place but the import of that same file in the same cube on development does not finish. Sometimes the data is prepared but the file is not downloaded. Etc.

This topic is just to let you know that a number of these tickets lead to known defects and IBM are correcting them. First have a look at known defects before spending too much time or creating new support tickets.