Jump to content
Software FX Community

Exporting and the OLAP Extension


User (Legacy)

Recommended Posts

Posted

Greetings,

When exporting a chart using the OLAP Extension, I notice the data gets

exported as part of the Extensions node of the XML. This occurs even when

you use a FileMask setting that excludes data as part of the export. When

you import the chart, the data that appears as static.

We need to find a way to export a chart that uses the OLAP Extension, saving

the snapshot of the layout of the chart (dimensions selected, category bar

filters, etc.) and somehow make the data dynamic when the chart is imported.

Any ideas?

Thanks in advance for your help

Wendell Giedeman

Six Disciplines Corp.

  • 2 weeks later...
Posted

Hi,

We have been working on this issue and we feel we are very close to release

a new version that would support your scenario. I am posting this to make

sure we are on the right track.

Some background facts:

- When you export a chart we use the file mask which by default includes

everything (data, extensions and other settings not relevant for this

discussion)

- When you export a template we use a builtin file mask that does not

include data or extensions. Note that templates are important in this

discussion because we use them to support Personalized Charts.

- Saving data in an OLAP chart is key because we use this persisted chart on

the client side (web scenario) who has no access to the data layer.

- We cannot modify what gets saved by default because this would break

compatibility with existing apps

- When a chart with extensions is read, the previous list of extensions is

removed.

To support saving OLAP state with no data we are implementing the following

a) OLAP will honor the FileMask.Data flag. Note that even if you do not

change the MDX statement, just running at a different time may result in

different Dimension Levels or Values. In Time Dimensions executing the same

statement at the end of a year or the beggining of next year results in

different values (1997,1998 against 1997,1998,1999)

B) A new FileMask flag (FileMask.ReuseExtensions) that allows to read the

extension list reusing the objects (if the extension is already attached to

the chart)

In the new scenario you can add ReuseExtensions and remove Data from the

FileMask, then you can import this settings chart over a chart that already

has the OlapExtension with new data. Note that the order here is CRUCIAL,

data should be read first.

This solves the Windows Form scenario but not on the Web. We are considering

different options to allow personalized charts with OLAP state to be

persisted correctly.

We would appreciate any feedback you can provide,

JC

SoftwareFX Support

"Wendell G." <wgiedeman@sixdisciplines.com> wrote in message

news:fRR1NJZcEHA.3080@webserver3.softwarefx.com...

> Greetings,

>

> When exporting a chart using the OLAP Extension, I notice the data gets

> exported as part of the Extensions node of the XML. This occurs even when

> you use a FileMask setting that excludes data as part of the export. When

> you import the chart, the data that appears as static.

>

> We need to find a way to export a chart that uses the OLAP Extension,

saving

> the snapshot of the layout of the chart (dimensions selected, category bar

> filters, etc.) and somehow make the data dynamic when the chart is

imported.

> Any ideas?

>

> Thanks in advance for your help

>

> Wendell Giedeman

> Six Disciplines Corp.

>

>

>

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...