Function needed: saves slice and tableSize and formats then loads and applies to new data

Hello Franz,
 
Thank you for posting your question.
 
There could be several approaches to the application of slice, tableSizes and formats to new data.
 
The first approach requires providing data to the component by accessing a URL of a server-side script that returns data from the database in JSON format.
If it is a viable option for your application, then filename parameter can be used to provide JSON data, as follows:

{
 "dataSource": {
   "dataSourceType": "json",
   "filename": "https://your_script_that_returns_json_data"
 },
 "slice": {
   ...
 },
 "formats": [
   ...
 ],
 "tableSizes": {
   ...
 }
}

In this case, a user saves the whole report (slice/formats/tableSizes/etc and dataSource with the URL of a server-side script that returns data).
Setting this report later using setReport() API call will apply the slice/formats/tableSizes/etc from this report to the new data provided by the script "https://your_script_that_returns_json_data".
I have attached a sample report file to this answer (report-with-json-from-url.json)
Could you please let me know if this approach could work for you?
 
If you prefer to supply JSON data to the component through data parameter, as follows:

{
 "dataSource": {
   "data": jsonData
 }
}

then, in this case, the scenario can be implemented in a different way. If this option of providing JSON data works better for you, please let me know, and I will provide you with the instructions on this approach.
 
I'm looking forward to your answer.
 
Kind regards,
Iryna
 
 

Hello, Franz,
Thank you for providing more details about your use case.
Let me suggest you the following flow:

1. User opens the raw report. This report needs to have dataSource section, otherwise, it is not possible to configure slice, format, etc.
2. User fiddles with the report until it looks ok
3. User saves view (slice, format, etc.). This can be achieved by getting the current report via getReport() method, removing dataSource section, and saving this config.
4. User opens new data source and wants to apply the previous view. He selects the necessary view, and the new report is composed by merging getReport().dataSource with view configuration. Then this new report can be set via setReport().

So, as you can see, saving the full report, as usual, can be achieved with getReport(); saving current view should be done the same way, you just need to remove dataSource subobject.
Concerning your question about filename property, we recommend specifying all the necessary parameters here. For example:

filename: "http://olap.flexmonster.com/compressor/demo.php?parameter1=value1&parameter2=value2"

filename is either a URL to CSV or JSON file or a URL to the server-side script which generates data. Request Method for filename parameter is GET.
Please note that suggested scenario allows creating more than one slice version and saving it the way you need.
Let me know whether you were able to implement everything successfully.
Regards,
Tanya

Franz,
I would also like to mention that if GET Request Method of filename parameter does not work for your case, you can set JSON data via dataSource.data property:

{
"dataSource": {
"data": jsonData
}
}

In such case, the way how you get JSON data is completely up to you.
Regards,
Tanya

Franz,
We are glad you have managed to configure your app.
Let us know how the further process goes.
Regards,
Tanya