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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
PAW - "Remove" calculation in set editor should remove calculation from the query and not only from the current set
(See attached file for more details)
Idea Details: Use a real-life scenario to explain the problem statement/pain points,
End-users create calculation all the time in PAW views. When they don’t use it anymore, they simply remove the calculation from the selection in the set editor.
However, removing the calculation from the set editor doesn’t remove the calculation from the MDX query.
Since calculations have a strong impact on the performance of the view, end-users end up having slow views and they don’t understand why their view are slow (since they think they have properly removed calculation). That’s because they pay the price of the calculation still in the query despite the fact that they don’t use it.
In many cases, calculations stack up in the query over time, making the view very slow
state your current workaround(s),
With the guidance of an admin, they have to properly re-insert the calculations in the selection, recalculate the view and right-click on remove from the view to properly remove calculations from the query
state any proposed solution(s),
Removing a calculation from the selection using the set editor should remove the calculation from the query
state the benefits/value this idea has, state # of users impacted and how often are they impacted)
Making that change would result in a more consistent product behavior (removing calc from set editor would the same as removing from the view) and guarantee the stability of the performance.
Do not place IBM confidential, company confidential, or personal information into any field.