Is there a setting defining order of dimensions required in OLAPDataArea , creation vs alphabetical

Is there a setting defining order of dimensions required in OLAPDataArea command , creation vs alphabetical ?

We are migrating App Engine scripts from v11 to v12.

Existing scripts are failing when deleting OLAPDataArea, Initial analysis shows that the order of dimensions required in v11 was the order of dimension as created in the cube. It appears that in V12 it needs to be replaced with dimensions in alphabetical order. Is there a setting or command we can use to change this in v12 so all of the existing scripts work without changes ?

Or we need to replace all OLAPDataArea commands across our scripts, I assume we need to use something like the below to get the dimensions

OLAPDimensionList dimensionList = OLAPGetDimensionList(cube);

Thanks

David

Find more posts tagged with

Infor EPM Discussions

Comments

Nick Gladkov

David, no - version 11 and version 12 works same way here, so it should not be an issue (dimensions are in the order from cube creation, not alphabetical)

Nick Gladkov | Senior Product Manager, Infor d/EPM | Infor

d-wilcox

Ok Nick, I will ask developer for more details.
All other OLAP commands are working, just this one is throwing errors in every script.

From: Nick Gladkov
Sent: Tuesday, 29 September 2020 6:12 PM
To: dEPM-discuss@lists.inforcommunities.com
Subject: [dEPM-discuss] - RE: Is there a setting defining order of dimensions required in OLAPDataArea , creation vs alphabetical

David, no - version 11 and version 12 works same way here, so it should not be an issue (dimensions are in the order from cube creation, not alphabetical)

--

Nick Gladkov | Senior Product Manager, Infor d/EPM | Infor

-----End Original Message-----

Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering.
http://www.mailguard.com.au/mg

Report this message as spam https://console.mailguard.com.au/ras/1Z31uKB60m/4wcseK8vxo7CxaIK9KpMTb/5.6

--
Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering.http://www.mailguard.com.au/mg

unknown

David,

Can you please post the code for creating your data area, especially the code that populates the elements parameter (StringListList)? Also can you please post the error message?

In version 11, we used to use a StringList as the source for dimensions with multiple values in the filter. For example here is the syntax for 11

StringList slLevel = CreateStringList();

    Append(slLevel,"A");
    Append(slLevel,"B");
    Append(slLevel,"C");

StringListList sllPlug = CreateStringListList();
        Append(sllPlug, ConvertToStringList("ACTUAL"));
        Append(sllPlug, ConvertToStringList(OlapDataAreaBCells));
        Append(sllPlug, slLevel );
        Append(sllPlug, ConvertToStringList(OlapDataAreaBCells));

//--- Zero Out Target ---
OLAPDataArea daTargetPlug = OLAPCreateDataArea(olapConnection, consFinConCube, OlapDataAreaIncludeB, OlapDataAreaOperatorNone, 0,
OlapDataAreaOperatorNone, 0,sllPlug);

We received syntax errors when executing the zero out. We determined that the issue was the StringList we were using for multiple values in the dimension. We replaced it with a String Array and it works. Here is the new code

    StringArray slLevel = CreateStringArray();
    Append(slLevel,"A");
    Append(slLevel,"B");
    Append(slLevel,"C");

In addition, we have encountered time outs when running the zero out script in Version 12 Multitenant. In our case, we were trying to zero out all values for a particular level. We would time out because the account dimension was to large. In order to get around this issue, we had to loop through the account dimension, (fortunately the accounts we had to zero out were not that many) and zero out out the values for each account - level combination. This is certainly a time waster. It adds a whole minute to the process. I am contemplating creating a support ticket, but want to try it out with Version 12.10 first. I know the internal time out settings were increased and want to see if this fixes the problem.

ivan-rebo

Hi Bill,

maybe i can explain some details.

First, from your post its not clear what you do with the data area and what "zero out" mean. If you are actually writing zeroes to all the cells I would highly recommend, to rather delete the cells so they have no value. This is much faster and uses less resources on Olap side.

If you are already deleting cells (writing nulls), then please make sure to enable the zero suppression flag when creating the data area. This will create a data area only over the cells that are not already empty and will make it all much faster.

And finally for the issue with the string list. Its a bit complicated... Your script worked in 11.0 because it was less strict about some code bugs which in this case made it look like creating data area is actually easier then it is.

When passing the dimension filters to data area, the first parameter of each string list must either be an empty text (indicating the rest of the string list will be elements to filter by) or a selector (like OlapDataAreaBCells). So adding Append(slLevel, "") after creating the stringlist would fix your problem.

You might be confused why this isnt needed with StringArray or when you do ConvertToStringList("ACTUAL")... Thats because ConvertToStringList has some (ugly) hidden logic that automatically adds the empty space if the conversion isnt done from a selector... So if you do ConvertToStringList("ACTUAL") it actually produces a StringList with ("","ACTUAL"). Same when you convert the StringArray to StringList...

In 11.0 forgetting the empty space at the start usually worked out ok anyway even tho it was supposed to be supplied there too. In 12.x we are strict that it must be specified in case someone tries to filter by elements.

Copyright © 2025 Infor. All rights reserved.