About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
It is simply not acceptable to discount this request. There are many cases where PAW could be used for applications like CAPEX approvals, Compliance recording etc where some length of text responses may be required. Ideally I'd like to see further formatting ability within text cells as is available in some competitive products.
Do we want PA/PAW to be a player in the current market or do we want the developers life to be easy ? I appreciate what you are saying Stuart, but agree with comment on Feb 5th that this is an incorrect design, rather than an incorrect requirement.
If cells can handle long strings, which they can, then we need at least some basic format controls. Some of this was possible in Excel based interfaces, but we want to move forward.
It's hard to believe that in a world of analytics, consideration for commentary presented properly on a dashboard is not under consideration. Given the audiences of most dashboards the concepts of big data analysis and engagement with your customer base using word clouds and commentary on a proper RAG basis is paramount. Proper commentary handling (including word wrap) presentation should be high on the list. Also word wrapping on column is a real issue, and should be encompassed within this model, as it's then up to the dashboard designers to make them look good, rather than finding ways around Planning Analytics limitations.
Changed status to 'Not Under Consideration'. Text wrapping can have a very large impact on the cubeviewer as we now need to consider a variable row height. Row height is used to determine how much data should be pulled from the cube to present in Workspace. Users could enter string values that impact data visibility in the cubeviewer.
We current address this challenge using a tooltip on the cell to display the full string.
Seems more like an issue with the implementation of text strings in the exploration view than an enhancement as text is displayed fully in the cell when editing the contents.