TM1 Forum

Hi
I've created an RFE for the addition of new type of picklist definition MDX:{MDX Expression}.
Would like to try and avoid the creation of loads of redundant subsets to drive picklist selectors. All adds to the development time, server clutter and risk of deletion in error.

When we have to create a subset to get a piece of MDX in front of a user, the subset is redundant.

https://ibm-data-and-ai.ideas.aha.io/ideas/PAOC-I-318

As ever your votes would be appreciated!

(also can I encourage everyone in general to participate in the RFE process, IBM do use this as a guide when prioritising functionality)

Voted ! Thanks.

Also voted. I have been requesting this for years but I guess I never created a RFE for it.

Voted.

Looks like this one has made the cut - from the looks of some of the others that have previously made the cut, the comments added by others may weigh in when the ideas are picked, not only the no. of votes. The comments may highlight other use cases and bolster the case for inclusion. That's my thoughts at any rate - YMMV.

gtonkin wrote: ↑Mon Sep 14, 2020 5:39 pm Looks like this one has made the cut - from the looks of some of the others that have previously made the cut, the comments added by others may weigh in when the ideas are picked, not only the no. of votes. The comments may highlight other use cases and bolster the case for inclusion. That's my thoughts at any rate - YMMV.

Weeeellll... the status has changed to "Future Consideration", anyway. Lots of things are open for future consideration. I've considered the possibility of generating an income of half a million bucks per week and living on a country estate with a swimming pool just outside of Roma some time in the future. That doesn't mean that it's going to happen any time soon.

However I do agree that what the kids call "engagement" these days (votes, well argued comments, etc) probably helps with the shortlising process.