1. mike S
  2. PowerServer 2020 or older (Obsolete)
  3. Monday, 15 March 2021 14:16 PM UTC

I use decimal 28 precision in my powerserver 2020 application.

Other than being slower (as per the documentation) there have been other problems with using precision 28 (graphs apparently).  I am coming across decimal problems in PS 2020 that i don't believe were in 2016 and I am thinking that since precision 28 is not used nearly as much as 15 that it could be related to that.  (my issue is that powerscript variables defined as decimal are acting like real)

 

My question is this:  if you round to 16 decimal places, or have decimal{16} used anywhere while PS is set to precision 15, what exactly happens?  Does it ignore the 16 decimal places and simply use 15?  I think that 15 decimal places will work fine, but i would like to know what that setting actually does.

 

also, the help does say this: "is only supported in DataWindow"

does that mean that powerscript is already at decimal 15?  

 

 

Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 15 March 2021 14:57 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Mike,

This limitation is PowerServer 2020 is due to JavaScript language limitation, specifically in JavaScript it is a floating point.  Here is article explains what happens when you exceed the decimal precision in JavaScript: https://modernweb.com/what-every-javascript-developer-should-know-about-floating-points/

The 28 decimal precision only applies to the DataWindow, which we are doing in C++.  So my guess is if you are finding things dropping back down to lower precision it is because it is outside of this scope.  https://docs.appeon.com/ps2020/server_configuration_guide_for_net/ch04s04s04.html#d0e7645

With all that said, have you tried PowerServer 2021 to see if it mets your decimal precision needs?  On the client side is native PowerScript instead of translating to JavaScript.

Best regards,
Armeen

Comment
  1. Armeen Mazda @Appeon
  2. Monday, 15 March 2021 17:46 PM UTC
Hi Mike, Please open a support ticket with this finding... it could be a bug or it could be the documentation needs to be updated to explain this limitation better. Also, please give PowerServer 2021 a try!
  1. Helpful
  1. mike S
  2. Monday, 15 March 2021 18:25 PM UTC
i need this fixed for production immediately, so a PS2020 patch won't help; let alone 2021. I'm just trying to figure out what i have to do to get 2020 to work correctly with decimals.



I have done some 2021 testing, but since it doesn't automatically deploy the web services yet i would need time to figure that all out to see if it deploys' 100% before i can see how it works compared to PB. Plus, I need to know what powerserver features are not being supported, as well as how the supported powerserver features work since i heavily rely on powerserver web functionality. will there even be an AEM web application that goes along with it?

  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 15 March 2021 18:43 PM UTC
Please open a support ticket with your test case and we do our best to come up with a workaround. No way to get a fix immediately as it takes time to go through our QA process, plus if it is because of JS limitations then there is no fix.

The deploy of the Web services is easy... just use the “Publish” feature of SnapDevelop.

The list of unsupported features is in the documentation that comes with the beta version. It is single short page of stuff vs. hundreds of pages of unsupported stuff and limitations of the older PowerServer.

Their is no visual interface AEM. Instead you directly modify the values in basically an .INI file. The server APIs are exposed to be called directly in C# or you use the RESTClient.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.