This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
When writing multi-line MDX, the formatting is crucial to being able to read the code, debug and make updates at a later stage.
Saving the MDX without formatting means that the next time it is opened, you need to revisit the code, add in the formatting to make it readable once more.
This not only takes time but introduces risk to any updates, risk to the structure e.g. mixing up bracket positioning that can alter the way results are interpreted etc.
Consider the following MDX query:
TM1SORT({EXCEPT(FILTER(TM1FILTERBYLEVEL(TM1SUBSETALL([Product]) , 0) , [Product].CURRENTMEMBER.PROPERTIES("Local / Global") = "") , {[Product].[# Product]}),EXCEPT(GENERATE(FILTER(TM1FILTERBYLEVEL(TM1SUBSETALL([Product]) , 0) , [Product].CURRENTMEMBER.PROPERTIES("Profit Center") <> "") , {STRTOMEMBER("[Product].[" + IIF(STRTOMEMBER("[Product].[" + [Product].CURRENTMEMBER.PROPERTIES("Profit Center") + "]").FIRSTCHILD.PROPERTIES("Local / Global") <> [Product].CURRENTMEMBER.PROPERTIES("Local / Global") , [Product].CURRENTMEMBER.NAME , "# Product") + "]")}) , {[Product].[# Product]})} , ASC)
It will take a few minutes for someone opening that to unpack before being able to interpret what the code is actually doing and the likely result.
Consider that queries are used in both the Set editor and Cube viewer. Both areas would need to be enhanced to treat formatting the same way when saving and opening.
Needed By | Yesterday (Let's go already!) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This would make such a difference to utilising MDX in subsets. It is very frustrating when trying to do something clever like that example and it keeps going back to one line when you commit, which makes it much harder to troubleshoot.
Hello Stuart,
what is the current status for this idea?
Thank you in advance!
Vitalij
Updated to future consideration