Finally, THIS worked for me, thanks.
For those, who have 2-dim picklist cube: }Sandbox dimension can be used in columns, with "Base" sandbox only selected.
Original Message:
Sent: Tue February 13, 2024 12:34 AM
From: Johann Kassier
Subject: Planning Analytics Workspace Column Widths
Hi.
While we wait for the ability to define column width in an MDX statement (here's hoping!), one can get around this by setting the client as a context dimension rather than a column, and using a third dimension measure in the column. It does mean that you need a 3 dimension cube to store your user selections in, but that way you define the column width for the selected member, and that member doesn't change as different users open the workbook (only the context element changes). Also, you are still looking at a true IBM PA cell, so user can still input against that cell.
------------------------------
Johann Kassier
Original Message:
Sent: Mon February 12, 2024 11:16 AM
From: Mark Wragg
Subject: Planning Analytics Workspace Column Widths
Hi,
I am not a big fan of adding these calculations as they appear to be erratic, they cause issues I can't quite pin down, at least sometimes.
Even if it did work, I think it would be prudent to vote for the various ideas on this subject and hope IBM do something about it!
regards,
Mark
------------------------------
Mark Wragg
Original Message:
Sent: Fri February 26, 2021 04:33 AM
From: Mark Wragg
Subject: Planning Analytics Workspace Column Widths
Hi,
I have created filter selections for views in PAW using mdx.
Everything seems to work well except that when I save the book it does not save the column widths of views for other users.
Let me illustrate, when I create the book, add in the view, extend the column widths and save the book, the next time I open the book it remembers the column width as per the image below:
------------------------------
Mark Wragg
------------------------------
#PlanningAnalyticswithWatson