Planning Analytics

 View Only



LinkedIn Share on LinkedIn

Publishing Websheets from PAfE 2.0.99

By STUART KING posted Wed October 30, 2024 05:34 PM

  

This topic may be interesting to Planning Analytics for Excel users that publish Websheets to the Applications (Websheets in PAW) folder in the TM1 database.

Updating an existing Websheet in Planning Analytics for Excel simply deletes the original Websheet and upload a new Websheet with the same name.  This causes a problem if specific security was set on the Websheet.  Deleting the Websheet will cause the security and any other attributes to be removed.  Security is only a problem if permissions are set directly on the Websheet instead of the folder containing the Websheet.

Planning Analytics for Excel 2.0.99 provides solution for this problem.  There is a new feature that can be enabled in 2.0.99 that allows existing Websheets to be updated without removing existing security and attributes.  To enable this feature add the following to the tm1features.json file. 

"r99_EnableNewPublish" : true

If you are not already familiar with this configuration file please see the documentation here: https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=started-manually-enabling-features-in-tm1featuresjson-file.  Don't forget to restart Excel after updating the tm1feature.json file!

The Planning Analytics product team is looking for feedback on this change (comment below or reach out directly).  If this change proves to be useful then we will consider enabled the feature by default in later versions of Planning Analytics for Excel.

Two additional comments:

1 - If you have already moved to Planning Analytics on-premises 2.1 then the same change will be in the Planning Analytics for Excel 2.1.6 release.  This release should be available on Fix Central very soon.

2 - This change has no impact of versions of Planning Analytics using TM1 v12 (Planning Analytics SaaS on AWS).  

7 comments
53 views

Related Content

Permalink

Comments

Svetlana Pestsova
Thu November 07, 2024 09:08 AM

Expect that in the upcoming releases, most likely start of 2025.

Grischa Rehmer
Thu November 07, 2024 03:17 AM

I agree with Paul, it should be a default configuration.

But honestly, as I personally always set all the rights on }ApplicationSecurity via TM1-rules, this issue never happened to me before. One of my customers came to me and told me about this behaviour for manually maintained security.

Paul Coggan
Wed November 06, 2024 06:34 PM

This should definitely be the default configuration. I can't think of any scenario where it would not be desirable to retain the existing security settings on a published workbook. If security changes are required they can be applied in the normal way after publishing. Its definitely not desirable to be required to reapply after every template update.

Svetlana Pestsova
Wed November 06, 2024 09:36 AM

Grischa, that is correct for on-prem,

Best regards,

Grischa Rehmer
Wed November 06, 2024 02:30 AM

Thank you for the information and fix.

But this does mean, that any user that has the right to publish websheets needs to have this setting set in the tm1features.json file that is stored on their PC in the on-premise world, correct?

Filip Rufer
Wed November 06, 2024 02:25 AM

Thank you for this post. This is really good news. We will test this and roll it out. Our users will appreciate it.

Svetlana Pestsova
Wed October 30, 2024 08:23 PM

Just in addition to Stuart's good blog and because it's not mentioned in docs... after saving the tm1features.json, you'd need to close out of all Excel instances and then start Excel with PAfE to have the fix enabled.