Planning Analytics

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson

Good question Fred, we have the same issue. I'd like the default behaviour in PAW to act like a SUBNM with the first element in the subset displayed.

------------------------------
Kevin Bos
------------------------------

Original Message:
Sent: Thu June 17, 2021 11:44 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson

Hello Frederic,

I think PAW behavior is different and not sure if it will get this functionality

In our case we use stored values in parameter cubes to display current selection dynamically with MDX subset. Hope it can help.
I agree it is painfull for reporting.


Regards

------------------------------
Joseph GRANDCHAMP
------------------------------

Original Message:
Sent: Wed June 23, 2021 10:38 AM
From: Kevin Bos
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Good question Fred, we have the same issue. I'd like the default behaviour in PAW to act like a SUBNM with the first element in the subset displayed.

------------------------------
Kevin Bos

Original Message:
Sent: Thu June 17, 2021 11:44 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson

Hello Joseph 

thanks for you reply . 

we've done the same  sometimes but it's definitely not as simple and native as subsets . 

for me it's a small issue to solve for a huge improvement. 

what does IBM think about it ? 

Best regards 

fred 

------------------------------
frederic MALLAVAL
------------------------------

Original Message:
Sent: Thu June 24, 2021 06:04 AM
From: Joseph GRANDCHAMP
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Hello Frederic,

I think PAW behavior is different and not sure if it will get this functionality

In our case we use stored values in parameter cubes to display current selection dynamically with MDX subset. Hope it can help.
I agree it is painfull for reporting.


Regards

------------------------------
Joseph GRANDCHAMP

Original Message:
Sent: Wed June 23, 2021 10:38 AM
From: Kevin Bos
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Good question Fred, we have the same issue. I'd like the default behaviour in PAW to act like a SUBNM with the first element in the subset displayed.

------------------------------
Kevin Bos

Original Message:
Sent: Thu June 17, 2021 11:44 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson

Hi Fred,

Agree 100 %. We are also struggling with this and currently using parameter cubes but it comes with some downsides. 

I would also like to know if IBM has plans to address this. 

Regards,
Mario

------------------------------
Mario Hasler
------------------------------

Original Message:
Sent: Fri June 25, 2021 03:33 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Hello Joseph 

thanks for you reply . 

we've done the same  sometimes but it's definitely not as simple and native as subsets . 

for me it's a small issue to solve for a huge improvement. 

what does IBM think about it ? 

Best regards 

fred 

------------------------------
frederic MALLAVAL

Original Message:
Sent: Thu June 24, 2021 06:04 AM
From: Joseph GRANDCHAMP
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Hello Frederic,

I think PAW behavior is different and not sure if it will get this functionality

In our case we use stored values in parameter cubes to display current selection dynamically with MDX subset. Hope it can help.
I agree it is painfull for reporting.


Regards

------------------------------
Joseph GRANDCHAMP

Original Message:
Sent: Wed June 23, 2021 10:38 AM
From: Kevin Bos
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Good question Fred, we have the same issue. I'd like the default behaviour in PAW to act like a SUBNM with the first element in the subset displayed.

------------------------------
Kevin Bos

Original Message:
Sent: Thu June 17, 2021 11:44 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson

Hello Frédéric,
I totally agree. PAW is behaving in quite a weird way !
This is quite ennoying to stick to the element name instead of the subset rank number.
I've tried to see if something can be done using MDX statement for the dimension selector and I notice that with my PAW version 2.0.62, if keep the MDX result and not the MDX query so no success to achieve what you're trying to do.
@IBM this shouldn't be a big deal to fix...
Regards,​

------------------------------
Bob
------------------------------

Original Message:
Sent: Thu June 17, 2021 11:44 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson

Hello again,

I agree it should be a major defect.
I know populating cubes have some downsides, one major to me is error messages pup-up in PAW view when an MDX subset is empty.

We have user parameters empty first time they connect and it is really not friendly user. We have shown it to an IBM techsale who was horrify of this behavior. She said she will see what she can do but she also said we have to fill them ourselves before, so meantime I created an "idea" in the IBM Data. Feel free to vote for it:
https://ibm-data-and-ai.ideas.aha.io/ideas/PAOC-I-693

I will keep you updated if I know more

Regards,

------------------------------
Joseph GRANDCHAMP
------------------------------

Original Message:
Sent: Thu July 01, 2021 10:48 AM
From: Robert MILLI
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Hello Frédéric,
I totally agree. PAW is behaving in quite a weird way !
This is quite ennoying to stick to the element name instead of the subset rank number.
I've tried to see if something can be done using MDX statement for the dimension selector and I notice that with my PAW version 2.0.62, if keep the MDX result and not the MDX query so no success to achieve what you're trying to do.
@IBM this shouldn't be a big deal to fix...
Regards,​

------------------------------
Bob

Original Message:
Sent: Thu June 17, 2021 11:44 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson

Original Message:
Sent: 7/13/2021 9:47:00 AM
From: Joseph GRANDCHAMP
Subject: RE: PAW NOT USING SUBSET ELEMENT INDEX

Hello again,

I agree it should be a major defect.
I know populating cubes have some downsides, one major to me is error messages pup-up in PAW view when an MDX subset is empty.

We have user parameters empty first time they connect and it is really not friendly user. We have shown it to an IBM techsale who was horrify of this behavior. She said she will see what she can do but she also said we have to fill them ourselves before, so meantime I created an "idea" in the IBM Data. Feel free to vote for it:
https://ibm-data-and-ai.ideas.aha.io/ideas/PAOC-I-693

I will keep you updated if I know more

Regards,

------------------------------
Joseph GRANDCHAMP
------------------------------

Original Message:
Sent: Thu July 01, 2021 10:48 AM
From: Robert MILLI
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Hello Frédéric,
I totally agree. PAW is behaving in quite a weird way !
This is quite ennoying to stick to the element name instead of the subset rank number.
I've tried to see if something can be done using MDX statement for the dimension selector and I notice that with my PAW version 2.0.62, if keep the MDX result and not the MDX query so no success to achieve what you're trying to do.
@IBM this shouldn't be a big deal to fix...
Regards,​

------------------------------
Bob

Original Message:
Sent: Thu June 17, 2021 11:44 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson

Hello,

 

Thanks for the tip Paul. I am not comfortable by adding some dummy element in standard dimensions, but it may be the best workaround.

 

Here is the answer from the lab:

When building a view in a book and saving it. The state is persisted within the book. It is always expected that when opened the same view will render exactly how it was saved. If you have different requirements where you want the view to show dynamic selections based on your model changes in TM1, then you need to build that into your view using dynamic sets and expressions.

 

And 3 workarounds from tech sale:

• Use a MDX with a single element (but it forces to edit subset if you need to change)
• Save books on an out of scope element, then default selection automatically goes on new member (didn't try but I am pretty sure it is not working with picklist based on subset, as they can even display out of security scope elements)
• Use a MDX with a single element connected to a list widget (cf. gif, this one seems smart for standard dimensions, but I don't think widget can be easily updated plus it takes up space)

I also raised this question on "Ask me anything" session. The answer was simply it would have too many side effects on existing models with no more explanation. I can understand this point but why don't add an option to remove this behaviour.

I am wondering what the future of a tool replacing old clients by new bugged ones.

Fortunately, we will have soon Watson button.

 

Regards,

 

------------------------------
Joseph GRANDCHAMP
------------------------------

Original Message:
Sent: Wed July 14, 2021 07:24 PM
From: Paul Simon
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Hi Joseph

 

To get over the issue of showing a subset when nothing is selected, we have a zz_Select <dim name> element in every dimension. If nothing is selected we default it to this element to prompt the user to select something. All users are given read only access to this element, so they can all see it but no one can enter data against it.

 

I practice we normally record the user's last selection in a cube via a DBS and default the SUBNM to this, so the need for the zz_Select element only really applies to new users.

 

Regards

 

Paul Simon

 

Original Message:
Sent: 7/13/2021 9:47:00 AM
From: Joseph GRANDCHAMP
Subject: RE: PAW NOT USING SUBSET ELEMENT INDEX

Hello again,

I agree it should be a major defect.
I know populating cubes have some downsides, one major to me is error messages pup-up in PAW view when an MDX subset is empty.

We have user parameters empty first time they connect and it is really not friendly user. We have shown it to an IBM techsale who was horrify of this behavior. She said she will see what she can do but she also said we have to fill them ourselves before, so meantime I created an "idea" in the IBM Data. Feel free to vote for it:
https://ibm-data-and-ai.ideas.aha.io/ideas/PAOC-I-693

I will keep you updated if I know more

Regards,

------------------------------
Joseph GRANDCHAMP

Original Message:
Sent: Thu July 01, 2021 10:48 AM
From: Robert MILLI
Subject: PAW NOT USING SUBSET ELEMENT INDEX

Hello Frédéric,
I totally agree. PAW is behaving in quite a weird way !
This is quite ennoying to stick to the element name instead of the subset rank number.
I've tried to see if something can be done using MDX statement for the dimension selector and I notice that with my PAW version 2.0.62, if keep the MDX result and not the MDX query so no success to achieve what you're trying to do.
@IBM this shouldn't be a big deal to fix...
Regards,​

------------------------------
Bob

Original Message:
Sent: Thu June 17, 2021 11:44 AM
From: frederic MALLAVAL
Subject: PAW NOT USING SUBSET ELEMENT INDEX

paw can only refer to an element name of a subset and not the to an index .

if in a paw book  we use a named subset that presents the current month , for exemple MAR  from a subset that contains MAR FEB JAN 

if the next month we update the subset with APR,MAR,FEB,JAN  the PAW books stills open on MAR when i want him to open on the first element of the subset APR.

that makes reporting very difficult in PAW when there are dozens of books .

basically in a subnm you can use element name or index and that works in tm1web .

any idea or planned enhancement ?
regards
fred

------------------------------
frederic MALLAVAL
------------------------------

#PlanningAnalyticswithWatson