7 Replies Latest reply on May 29, 2018 3:57 PM by sroux

Remove unspecified / ASO: not working?

sroux May 29, 2018 2:57 PM

Hi,

Following many tests it looks like that Maxl command import dimension is not working properly with remove unspecified option (11.1.2.3.500) on ASO.

Indeed new members are added following / below the existing list of members and are not being arranged as specified in input file.

After further testing, new members are arranged as specified in input file if I manually delete dimension content + save...

ie. INPUT FILE (parent child)

Entity _ TOTAL

TOTAL _ L001

TOTAL _ L002

TOTAL _ LNEW

TOTAL _ L003

it will result in :

Entity

_ TOTAL

__ L001

__ L002

__ L003

__ LNEW

My data load rule has the folowing options enabled :

- Allow property changes

- Allow formula changes

- Allow UDA changes

- Remove unspecified

Has anyone observed such behavior with ASO...! Thank you

1. Re: Remove unspecified / ASO: not working?

TimG May 29, 2018 3:00 PM (in response to sroux)

I don't understand from your example how this is a test of "remove unspecified". I don't associate "remove unspecified" with sort order.

I've definitely seen the behavior where new members are always 'tacked on' at the bottom of the list though.
Like Show 0 Likes(0)

Actions
2. Re: Remove unspecified / ASO: not working?

sroux May 29, 2018 3:22 PM (in response to TimG)

Hi Tim, thx for getting in... indeed I am not speaking about sort order but just input file order.

What I mean is that for an existing ASO dimension new members will be created at the end (after last sibling) and not placed or ordered as specified in the file.

So not only members are not correctly ordered but created "at the end" and also remove unspecified option does not seems to help here... I did not tested with 11.1.2.4 yet.
Like Show 0 Likes(0)

Actions
3. Re: Remove unspecified / ASO: not working?

TimG May 29, 2018 3:22 PM (in response to sroux)

OK, yes - this is the behavior I've always seen. I don't think I've ever expected "remove unspecified" to help with this - am I misunderstanding you?
Like Show 0 Likes(0)

Actions
4. Re: Remove unspecified / ASO: not working?

GlennS_3 May 29, 2018 3:24 PM (in response to TimG)

The only way this will work is to have a dummy file with a single member in it and use remove unspecified in the rule. then process that file and your real file (in a single MaxL statement) it will drop all members except the one then add the members back in from your real rule. It will put them in order
Like Show 1 Likes(1)

Actions
5. Re: Remove unspecified / ASO: not working?

sroux May 29, 2018 3:36 PM (in response to TimG)

Indeed you are right Tim, however this is not the case in BSO (and without mentioning "remove unspecified")...
Like Show 0 Likes(0)

Actions
6. Re: Remove unspecified / ASO: not working?

TimG May 29, 2018 3:40 PM (in response to sroux)

Really? I did not know that was a BSO/ASO difference.

I think I've always used the approach Glenn mentions, or had a 'template' outline with none of the child hierarchies as my starting point.
Like Show 0 Likes(0)

Actions
7. Re: Remove unspecified / ASO: not working?

sroux May 29, 2018 3:57 PM (in response to TimG)

Thank you guys, Tim and Glenn.

I created and batched the template in order to initialize the build process the concerned ASO cube.

Isn't this the beauty of Essbase... learning new stuff everyday even after 15 years of practice..?!

Tim just try it once because this something I spotted while working on an ASO project, could be related to the version being used 11.1.2.3.500. I will check on 11.1.2.4 and advise further on.

Have a god day.
Like Show 1 Likes(1)

Actions

Go to original post