Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com
------------------------------

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi Stuart:

Thanks for the quick clarification! I should have paid more attention to the description on the APAR. Yes this is PA Local. Would you still see any scenario where going to 2.1.7 may be helpful?

As I rebuild I will be on the lookout for expanded websheet report area issues.

Thank you!

AG

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi AG, what are the file sizes of the non-working websheets in the }Externals folder after re-publishing from PAfE?

Hi Stuart:

Thanks for the quick clarification! I should have paid more attention to the description on the APAR. Yes this is PA Local. Would you still see any scenario where going to 2.1.7 may be helpful?

As I rebuild I will be on the lookout for expanded websheet report area issues.

Thank you!

AG

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi Vlad:

The file sizes are not very different between the original working workbook published from Perspectives and the not-working saved-from-PAfE workbook. Both are small at around 147 kB despite having 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection.

I am going through the exercise of re-adding sheets one by one until it breaks. There's definitely something that causes the JVM to run out of memory (per the tm1web.log file).

Thank you,

AG  

Hi AG, what are the file sizes of the non-working websheets in the }Externals folder after re-publishing from PAfE?

Hi Stuart:

Thanks for the quick clarification! I should have paid more attention to the description on the APAR. Yes this is PA Local. Would you still see any scenario where going to 2.1.7 may be helpful?

As I rebuild I will be on the lookout for expanded websheet report area issues.

Thank you!

AG

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Hi Vlad:

The file sizes are not very different between the original working workbook published from Perspectives and the not-working saved-from-PAfE workbook. Both are small at around 147 kB despite having 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection.

I am going through the exercise of re-adding sheets one by one until it breaks. There's definitely something that causes the JVM to run out of memory (per the tm1web.log file).

Thank you,

AG  

Hi AG, what are the file sizes of the non-working websheets in the }Externals folder after re-publishing from PAfE?

Hi Stuart:

Thanks for the quick clarification! I should have paid more attention to the description on the APAR. Yes this is PA Local. Would you still see any scenario where going to 2.1.7 may be helpful?

As I rebuild I will be on the lookout for expanded websheet report area issues.

Thank you!

AG

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

I had an issue with a large Perspectives report that I was transitioning to PAfE. The fix for me was to copy all the sheets into a fresh new Excel book. I copied them over one by one to check which of them tipped it over the edge but then after moving all of them it worked just fine. I put it down to something I couldn't see lurking around in an old version of the original Excel book it was created in.

Hi Vlad:

The file sizes are not very different between the original working workbook published from Perspectives and the not-working saved-from-PAfE workbook. Both are small at around 147 kB despite having 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection.

I am going through the exercise of re-adding sheets one by one until it breaks. There's definitely something that causes the JVM to run out of memory (per the tm1web.log file).

Thank you,

AG  

Hi AG, what are the file sizes of the non-working websheets in the }Externals folder after re-publishing from PAfE?

Hi Stuart:

Thanks for the quick clarification! I should have paid more attention to the description on the APAR. Yes this is PA Local. Would you still see any scenario where going to 2.1.7 may be helpful?

As I rebuild I will be on the lookout for expanded websheet report area issues.

Thank you!

AG

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

Thanks Lindsey!

Yes indeed, the step by step rebuild is the tried-and-true method for getting this done when all else fails!

And so far it's been helping me find the issues which so far - interestingly - relate to inefficient MDX expressions in dynamic reports. What's puzzling is that this same workbook, with these same MDX expressions, has been working fine in "old" Perspectives/TM1 Web for years but in the new world are causing the Java Virtual Machine to run out of memory!

Thanks,

AG

I had an issue with a large Perspectives report that I was transitioning to PAfE. The fix for me was to copy all the sheets into a fresh new Excel book. I copied them over one by one to check which of them tipped it over the edge but then after moving all of them it worked just fine. I put it down to something I couldn't see lurking around in an old version of the original Excel book it was created in.

Hi Vlad:

The file sizes are not very different between the original working workbook published from Perspectives and the not-working saved-from-PAfE workbook. Both are small at around 147 kB despite having 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection.

I am going through the exercise of re-adding sheets one by one until it breaks. There's definitely something that causes the JVM to run out of memory (per the tm1web.log file).

Thank you,

AG  

Hi AG, what are the file sizes of the non-working websheets in the }Externals folder after re-publishing from PAfE?

Hi Stuart:

Thanks for the quick clarification! I should have paid more attention to the description on the APAR. Yes this is PA Local. Would you still see any scenario where going to 2.1.7 may be helpful?

As I rebuild I will be on the lookout for expanded websheet report area issues.

Thank you!

AG

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

------------------------------
Philippe CHAMPLEBOUX
EPM Project director
Next Decision
NANTES

Original Message:
Sent: Wed January 15, 2025 09:02 AM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Thanks Lindsey!

Yes indeed, the step by step rebuild is the tried-and-true method for getting this done when all else fails!

And so far it's been helping me find the issues which so far - interestingly - relate to inefficient MDX expressions in dynamic reports. What's puzzling is that this same workbook, with these same MDX expressions, has been working fine in "old" Perspectives/TM1 Web for years but in the new world are causing the Java Virtual Machine to run out of memory!

Thanks,

AG

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Wed January 15, 2025 04:12 AM
From: Lindsey Brooks
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

I had an issue with a large Perspectives report that I was transitioning to PAfE. The fix for me was to copy all the sheets into a fresh new Excel book. I copied them over one by one to check which of them tipped it over the edge but then after moving all of them it worked just fine. I put it down to something I couldn't see lurking around in an old version of the original Excel book it was created in.

------------------------------
Lindsey Brooks

Original Message:
Sent: Tue January 14, 2025 02:33 PM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi Vlad:

The file sizes are not very different between the original working workbook published from Perspectives and the not-working saved-from-PAfE workbook. Both are small at around 147 kB despite having 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection.

I am going through the exercise of re-adding sheets one by one until it breaks. There's definitely something that causes the JVM to run out of memory (per the tm1web.log file).

Thank you,

AG  

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Tue January 14, 2025 02:00 PM
From: Vlad Didenko
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi AG, what are the file sizes of the non-working websheets in the }Externals folder after re-publishing from PAfE?

------------------------------
Vlad Didenko
Founder at Succeedium
TeamOne Google Sheets add-on for IBM Planning Analytics / TM1
https://succeedium.com/teamone/
Succeedium Planning Analytics Cloud Extension
https://succeedium.com/space/

Original Message:
Sent: Tue January 14, 2025 12:52 PM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi Stuart:

Thanks for the quick clarification! I should have paid more attention to the description on the APAR. Yes this is PA Local. Would you still see any scenario where going to 2.1.7 may be helpful?

As I rebuild I will be on the lookout for expanded websheet report area issues.

Thank you!

AG

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Tue January 14, 2025 12:33 PM
From: STUART KING
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

------------------------------
Stuart King
Product Manager
IBM Planning Analytics

Original Message:
Sent: Tue January 14, 2025 12:15 PM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Tue January 14, 2025 09:12 AM
From: STUART KING
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

------------------------------
Stuart King
Product Manager
IBM Planning Analytics

Original Message:
Sent: Mon January 13, 2025 04:50 PM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com
------------------------------

Hi Philippe:

Thank you for asking this question, and I am very interested in hearing from @STUART KING or maybe even @Hubert Heijkers as to why this dynamic report performs so differently between the two versions - note though that this is ALL PA Local, and I am not sure how much it would apply to PA SaaS:

• The OLD version published from Perspectives to TM1 Web 2.0.x has been working acceptably since 2019
•  But when republished from PAfE 2.1.1 to TM1 2.1.1 the JVM ran out of memory and in one case crashed the TM1 Web service.

The Excel file has about 20 sheets and publishes to the same small file size, but has several dynamic reports. So far I have found one sheet that was causing a problem (I do not know if this is the ONLY one, but it was certainly a part of it).

Here's the structure of the MDX that was working fine when published from Perspectives (since 2019), but which caused problems when republished from PAfE in 2025:

{ HIERARCHIZE(

{TM1FILTERBYLEVEL(

{FILTER(  {TM1SUBSETALL([ dimension ])},  FilterCondition1 }

+ {FILTER(  {TM1SUBSETALL([ dimension ])},  FilterCondition2 )}, 0 )})}

Here's the new MDX that resolved/improved the situation:

{ HIERARCHIZE(

{FILTER(  {TM1FILTERBYLEVEL(TM1SUBSETALL([ dimension ]), 0)},

FilterCondition1 OR FilterCondition2)}

)}

As you can hopefully see, the second one requires fewer filter iterations, and the filter conditions may be quite expensive as they involve cube look ups but ultimately they are not wildly different in complexity. I expect the HIERARCHIZE (sort) step to be the most expensive, but in both cases the input set should be similar in size. I should add that I am not sure what HIERARCHIZE is doing for us when everything is filtered to level 0 anyway :-) but right now I am more focused on optimizing syntax than semantics and minimizing functional changes. 

If anything I thought MDX processing would be more efficient in the new world :-)

I'll try and look up your ticket but because I am in PA Local which is quite different from PA SaaS I am not sure how comparable they are. However, perhaps there are some code overlaps somewhere - perhaps in the PAfE piece? - that this example may help narrow down?

Best regards,

AG 

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Wed January 15, 2025 09:14 AM
From: Philippe CHAMPLEBOUX
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

------------------------------
Philippe CHAMPLEBOUX
EPM Project director
Next Decision
NANTES

Original Message:
Sent: Wed January 15, 2025 09:02 AM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Thanks Lindsey!

Yes indeed, the step by step rebuild is the tried-and-true method for getting this done when all else fails!

And so far it's been helping me find the issues which so far - interestingly - relate to inefficient MDX expressions in dynamic reports. What's puzzling is that this same workbook, with these same MDX expressions, has been working fine in "old" Perspectives/TM1 Web for years but in the new world are causing the Java Virtual Machine to run out of memory!

Thanks,

AG

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Wed January 15, 2025 04:12 AM
From: Lindsey Brooks
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

I had an issue with a large Perspectives report that I was transitioning to PAfE. The fix for me was to copy all the sheets into a fresh new Excel book. I copied them over one by one to check which of them tipped it over the edge but then after moving all of them it worked just fine. I put it down to something I couldn't see lurking around in an old version of the original Excel book it was created in.

------------------------------
Lindsey Brooks

Original Message:
Sent: Tue January 14, 2025 02:33 PM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi Vlad:

The file sizes are not very different between the original working workbook published from Perspectives and the not-working saved-from-PAfE workbook. Both are small at around 147 kB despite having 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection.

I am going through the exercise of re-adding sheets one by one until it breaks. There's definitely something that causes the JVM to run out of memory (per the tm1web.log file).

Thank you,

AG  

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Tue January 14, 2025 02:00 PM
From: Vlad Didenko
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi AG, what are the file sizes of the non-working websheets in the }Externals folder after re-publishing from PAfE?

------------------------------
Vlad Didenko
Founder at Succeedium
TeamOne Google Sheets add-on for IBM Planning Analytics / TM1
https://succeedium.com/teamone/
Succeedium Planning Analytics Cloud Extension
https://succeedium.com/space/

Original Message:
Sent: Tue January 14, 2025 12:52 PM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi Stuart:

Thanks for the quick clarification! I should have paid more attention to the description on the APAR. Yes this is PA Local. Would you still see any scenario where going to 2.1.7 may be helpful?

As I rebuild I will be on the lookout for expanded websheet report area issues.

Thank you!

AG

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Tue January 14, 2025 12:33 PM
From: STUART KING
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi AG,

That APAR is very specific to the Planning Analytics SaaS (on AWS or Azure) offering.  The new SaaS offering does not yet use the 2.1.x versioning.  I'm assuming this is on-premise because you have access to the tm1web.log file.

I'm suggesting the Websheet report area somehow became much larger when it was opened and published from PAfE.  This could cause the PASS service to run our of memory (consistent with what George suggested).  Note that the TM1Web memory settings are not found in Cognos Configuration in current releases.  Please see: https://www.ibm.com/support/pages/how-manage-your-tm1-application-server-java-memory  

------------------------------
Stuart King
Product Manager
IBM Planning Analytics

Original Message:
Sent: Tue January 14, 2025 12:15 PM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Stuart:

Is this what you were referring to when you suggested retesting in 2.1.7? "PH61584: LARGE CUSTOM WEBSHEETS DO NOT RENDER AFTER UPGRADING TO PLANNINGANALYTICS AS A SERVICE" (https://www.ibm.com/mysupport/s/defect/aCIKe00000001iY/dt386636?language=en_US)

If so, are you in a position to provide any details on what was actually fixed here? Also please confirm that both PASS and PAfE would need to be updated?

The reason I am asking is because this client is a large, very security and audit-conscious organization, so the process to "try a different release" requires some justification.

Beyond that I can tell you that the file sizes are not different between the original Perspectives workbook and the saved-from-PAfE workbook, and small at around 147 kB despite the 20+ sheets which are almost all dynamic reports saved in an "unexpanded" state by specifying a blank (error) default SUBNM selection. 

According to the tm1web.log file, it does look as though the JVM ran out of memory (heapspace) (thanks George), so I am going through a rebuild exercise to figure out where the breakpoint is.

Thanks again!

AG

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com

Original Message:
Sent: Tue January 14, 2025 09:12 AM
From: STUART KING
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi AG,

If you save the file to disk from PAfE is the file size much bigger than the original report file in Perspectives?  Hopefully you have a copy of the file from before it was opened in PAFE.  Maybe this is just the old problem where the report area that is defined by the Excel client is much bigger than it needs to be (e.g the report area somehow became all columns, including the empty columns to the right, in Excel).

I did quickly check with our development lead for PAfE and PASS.   They confirmed that PASS simply deserializes the content in the Excel file.  PASS does not know if the websheet was published from Perspectives or PAfE. 

Worth noting that PAfE 2.1.1 is actually a bit behind now.  We added this table (https://www.ibm.com/docs/en/planning-analytics/2.1.0?topic=21-understanding-planning-analytics-local-component-versions) to our documentation to explain the relationship between the 2.0.x and 2.1.x releases of each Planning Analytics component.  Might be worth retesting in PASS 2.1.7 in case there is a performance issue we addressed. 

------------------------------
Stuart King
Product Manager
IBM Planning Analytics

Original Message:
Sent: Mon January 13, 2025 04:50 PM
From: Ann-Grete Tan
Subject: Moving TM1 Web websheet maintenance from Perspectives to PAfE (Help?)

Hi everyone:

I am looking for someone to "sanity check" the experience that I am about to describe. Is it only me? Am I missing some vital piece of intelligence? THANK YOU!

Here's the story: since Perspectives is going away, we are republishing all our TM1 Web websheets from Planning Analytics for Excel (PAfE 2.1.1) to make sure they can be maintained going forward.

There are some things we expected to need to change/fix including Action Buttons, and some of our dynamic reports (TM1RPTROW) since PAfE is a little less forgiving of some omissions. Mostly things have progressed well.

But we have a couple of large websheets (with ~20 sheets) that won't even open in TM1 Web after being republished from PAfE but for which the old Perspectives-published edition opens INSTANTANEOUSLY in our old TM1 Web 2.0.x. The contrast is striking!

Does anyone have any wisdom they can share INCLUDING (perhaps) some insights into how the PAFE-published websheets are processed differently from the Perspectives-published ones? 

Surely I am not the only person running into this?

Thank you.

A.G.

------------------------------
Ann-Grete Tan
agtan@tensorresearch.com
------------------------------