Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi Stuart,

Realise this thread is a few years old now but was wondering where your testing landed. 

This capability is still not available as far as I can tell, but would enable cascading prompts which would be hugely beneficial for filtering views with many hierarchies and sparse data.

Cheers,

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi Luke,

The limitation identified in the original post is still valid in current versions of Workspace today.  While there have been signifigant improvements to synchronization since 2021, this specific limitation still needs to be addressed.  I can confirm it's still on our radar.  We have a major synchronization enhancement, specific to the context passing when using buttons to navigate between books, coming in Workspace 2.0.99 in October.  We should be able to start investigating solutions to address this limitation after that.       

The current workaround is still use Websheets.  

Hi Stuart,

Realise this thread is a few years old now but was wondering where your testing landed. 

This capability is still not available as far as I can tell, but would enable cascading prompts which would be hugely beneficial for filtering views with many hierarchies and sparse data.

Cheers,

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark

Hi Stuart,

Realise this thread is a few years old now but was wondering where your testing landed. 

This capability is still not available as far as I can tell, but would enable cascading prompts which would be hugely beneficial for filtering views with many hierarchies and sparse data.

Cheers,

Hi, 

I have run into an issue in PAW and wondered if anyone had a workaround or if IBM were planning any work to address the issue. 

The issue is as follows:

I have created 2 attributes for the Version dimension, these attributes are called Start Year and End Year. I can reference these attributes in MDX for the Year dimension, I can then have a view in workspace and when a user selects a version it will only return the years between the version Start Year and End Year.

The MDX is as follows:

{TM1FILTERBYLEVEL({FILTER( {TM1SUBSETALL([1002.00 Year])}, left([1002.00 Year].currentmember.name,4)>= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[Start Year]),4) and left([1002.00 Year].currentmember.name,4) <= Left([}ElementAttributes_0001.00 Version].([0001.00 Version].currentmember, [}ElementAttributes_0001.00 Version].[End Year]),4))},0)}

If I add a cube view to the workspace sheet and then update the Year dimension with the above mdx this works fine, the years change depending on the version selected.

The following image shows a version with a start year of 2019/2020 and an end year of 2021/2022

The problem occurs if I want to drag the version and year dimensions outside of the cube view, when this happens the year no longer appears to know which version is the current member, so it seems I am not able to use this MDX in these situations. This is really limiting as I would like to hide the dimensions from the user. Synchronising the dimensions also doesn't work.

The below image shows the version and year dragged outside the cube view: 

As can be seen from the image above the years do not show correctly. 

Does anyone have any workaround for this? Does PAW already deal with this and I am missing something?

regards,

Mark