TM1 Forum

Hi,

I have a subnm selection box that does not update properly (not after rebuild sheet/book), only after double clicking.

I have a process that adds a new element to a dimension (insert direct). After refreshing, my dynamic report is updated, but my subnm selection list isn't. Both depart from the same mdx subset (base).
I added 2 screenshot to illustrate the discrepancy between the two (in one I have 'Q' in the other I have 'S').

Dynamic subset:
Base = TM1FILTERBYLEVEL(TM1SUBSETALL([Share category]) , 0)
A selection box:
SUBNM(ServerDimension;"Base";elementName)
A dynamic report
TM1RPTROW($B$12;ServerDimension;"Base")

Is this a known issue?

Hi

You didn't show the SUBNM

Does it by any chance identify the element in something in double quotes rather than an index number? If the value for the element is given in quotes, then it will always show that value whether it is in the subset or not. It you give an index it will show the element at that position in the subset

Regards

Paul Simon

paulsimon wrote: ↑Wed Nov 25, 2020 8:23 pm Hi

You didn't show the SUBNM

Does it by any chance identify the element in something in double quotes rather than an index number? If the value for the element is given in quotes, then it will always show that value whether it is in the subset or not. It you give an index it will show the element at that position in the subset

Regards

Paul Simon

Paul,

The SUBNM was written in the post.
I guess the issue is that you seem to not be able to select the new element in what should be a dynamic subset in the SUBNM, while it works fine in te active form.

Hi

Sorry I missed the SUBNM in the post. Can you confirm it is a name not an index? You would probably still need it to be an index for it to show the revised element selection.

In the process that adds the element do you have a RefreshMDXHierarchy( vDim ) in the Epilog?

Another possibility might be a DimensionUpdateDirect, however, I would try the other items first.

Regards

Paul

paulsimon wrote: ↑Wed Nov 25, 2020 11:38 pm Sorry I missed the SUBNM in the post. Can you confirm it is a name not an index? You would probably still need it to be an index for it to show the revised element selection.

In the process that adds the element do you have a RefreshMDXHierarchy( vDim ) in the Epilog?

Another possibility might be a DimensionUpdateDirect, however, I would try the other items first.

Hi,

I can select the new element by referencing the index, after that the SUBNM is shown correctly.
However, I want to be able to select the new element after I run the process.
Both RefreshMDXHierarchy and DimensionUpdateDirect are ineffective.

Tnx,
Felix

Hi Felix,

I'd suggest you reference the MDX directly in the report row formula, rather than indirectly via the subset. This ought to resolve / workaround the issue.

One of the other arguments allows you to reference a MDX directly, you'll need to take away the reference to the subset as well.

Cheers,

Hi,

If you select the SUBNM cell and go to "Data Validation" you will see that the drop down list that you are seeing (as shown in your SUBNM.png image) is an Excel generated list rather than one generated by PAX. It will have a source called something along the lines of "Cafe_Validation_Temp".

I believe that the Excel validation list is ONLY generated when you double click in the cell and go to the proper subset editor window, so the list is just provided as a shortcut way for you to make selections but it needs a prompt for it to refresh that list... and that prompt is you double clicking into the SUBNM cell.

You will also notice that if you add a new SUBNM to a sheet, that the Excel validation list doesn't appear until AFTER the first time you double click in to the cell.

Of course none of the above helps when it comes to actually overcoming the desire you have for the list to be refreshed automatically.
I did a quick test to see if you can set your own Excel Data Validation list over the SUBNM cell but as expected it gets replaced by the auto generated one.

I would suggest perhaps asking the question over at the IBM forum as it is frequented by IBMers who often prompt ideas or take the problems away to the development team if there isn't a solution/workaround already available:
https://community.ibm.com/community/use ... updetails

Thanks,
Declan

Thanks for the responses.

Steve Rowe wrote: ↑Fri Nov 27, 2020 11:22 am I'd suggest you reference the MDX directly in the report row formula, rather than indirectly via the subset. This ought to resolve / workaround the issue.

One of the other arguments allows you to reference a MDX directly, you'll need to take away the reference to the subset as well.

In the SUBNM function it is not possible to directly reference a MDX statement, (the TM1RPTROW function works perfectly.)

Denclanr gave a good explanation why SUBNM is not working as expected.

Tnx,
Felix