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 updateson 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
I am using PAfE version 76. When I use the SUBNM formula:
I get the result as ACT.
When I change the case and use the SUBNM formula:
I get the result as act.
Surely only one of them is a valid element in the Scenario dimension, not both.
Even worse, for instance this can occur as well:
=SUBNM( "Correct servername:Sp_Bogus", "", "TEST VALUE THAT DOES NOT EXIST IN DIMENSION")
When the server name is incorrect we get an error. Fine.
However, once the server name is fine, we can enter wrong dimension names, wrong element names...
They all pass and are shown as the result of the SUBNM formula. To me this makes no sense at all. They do not exist in the dimension ! The user / report builder cannot spot issues easily, only through DBRW formulas that point to the cells. Any SUBNM that is not used in DBRW formulas (for instance, to pass element names from one sheet to another) will have errors baked in potentially. An incorrect dimnension name, not existing element names, not existing alias name or subset, these are cases that should be validated when the SUBNM is entered - to avoid issues down the line.
Do not place IBM confidential, company confidential, or personal information into any field.