Some of our dashboards are using a lot of data. We are looking into the possibilities of using 'datamart' iok files in order to decrease the dataload in the local Omniscope files. If I understand correctly, it works as follows:
1. IOK file that is the server-based datamart file, and has all the source data in it. 2. Dashboard IOK File, that has the datamart IOK file as its source.
Now I would like to load only the selected data from the 'datamart' file into the local 'dashboard' IOK. For example, I have visits of representatives of all 2013 in my server-based 'datamart' file, but I only want the last 2 weeks refreshed into the local 'dashboard' Omniscope report IOK.
The selection of the data would be done by the end-user and is exactly what I need. Where do I start? Is there an instruction or demo file that I can look into?
This is an example where local selection is transmitted not only back to a central IOK 'staging' datamart, but even further back to parameterised queries that hit the source repository.
An overview of a typical multi-file reference architecture is attached.
HI Thomas, thanks for the rapid response. I saw the video and dived in the info you posted. I believe this is not what I meant.
I would like to publish an iok file (dataExplorer) that has no or little data in it. But when the end user makes the desired selection, omniscope retrieves the needed data from the 'datamart' file that is stored on our server. This way only the selected data will be in the local omniscope of the end-user. This will result in lower data load and better performance.
Alex - The issue is whether you can pre-define the subset of the 'datamart' to be shipped to specific recipients at specific times, or whether the end-users need free choice to define the subset they want 'on-the-fly'.
IF you can centrally pre-define the subset to be delivered every day/week, then the Batch Distribution control file (Server/ServerPlus only) allows you to specify per-report, per-recipient filters that will ship only the required subset of fields/columns and rows/records to each recipient in a totally automated refresh/filter and delivery process. If you have ServerPlus, you can refine this to automate live refresh of only the pre-defined subset direct to the user's desktop. If you have only a legacy Server Edition, you will need to automatically deliver a new copy of the file containing only the most recent subset drawn from the central 'datamart' as defined in the Batch Distribution control file and automated in the Scheduler Task List.
IF, however, the end users need to be able to define the relevant subset to refresh 'on-the-fly', e.g...a start and end date for a subset of a time series, this is done using parameter passing. The Report IOK file needs to be configured with parameters determining which subset of the central 'datamart' source needs to be loaded into the local file on refresh. Parameter passing is not intended to work from an un-enabled IOK file opened in a free Viewer, but ServerPlus enabling of some of this parameter passing from free Viewers has been mooted as an Idea.