The material provided is for informational purposes only, and should not be relied on in making any purchasing or investment decision. The information is not a commitment, promise or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. © 2026 Cloud Software Group, Inc. All rights reserved
Thanks for the explanation. I am sure you are aware of that for in memory data tables you can export the data to the library?
In general you are right. However I do not want to export just the information that is visualised, but alle the data behind it.
For instance we have a db table that holds 1mio transactions, in a summary visualisation I only show 4 rows based on the sales region the sales fall into. what i would like to do is to export the full 1mio rows as a SBDF file into the library to be able to work with them in other visualisations. what i managed to do so far was export the 4 rows that represent the summary. however, that is not sufficient enough.
Hi Martin, thanks for contributing your idea. To make sure I get it, is your use case that you would like to be able to connect to a database but keep the data external, configure a visualization like a cross table, and then export the data from the cross table as an SBDF and store it in the library?
Are you thinking that this is something done interactively, or do you see it as part of some automated flow?