Hi there we are currently experiencing some bizarre behaviour with the formatting of a decimal variable within standard BC String functionality.
The problem manifests itself within StrSubstNo (also in Message and Error).
It was first noticed in the 'RecordDetails' function within the Approval Entry table.
The line: show below causes the error.
I have added a subscriber to bypass this with the following code:
Just for testing - we get the resultant page now displaying.
As you can see from the code snippet, if the value is assigned to a local variable, then this is okay...
There is a new option on the page, to enable us to show the amount firstly, having been assigned in a 'confirm dialogue' then the field is used directly in the 'message' window - and breaks!
I suspect that it has to do with the 'Precision' element of the format string - but we have no control over this... the field itself is a standard field on the Approval Entry table.
I guess it could be something to do with the 'AutoFormatExpression' property,,, but this cannot be the only field using this.
Any help would be gratefully received.. as we don't want to have to bypass all functions where this could possibly happen!
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,104 Most Valuable Professional
nmaenpaa 101,156