| |
Results |
|
Using AppScript and DateAdd function to increment date by month can result in error: "Numeric overflow -- ERR #2 Line X"
|
You use the following vbscript function to add 1 month to this date DateAdd(m, 1, "1/31/2015") This will result in the error " Numeric overflow -- ERR #2 Line X" because SBM is actually trying to add a month to "1/31/2015" so the result would be "2/31/2015" which there is no Feb. 31 so it throws an error.
|
|
|
|
Killer Import Error: ORA-01426: numeric overflow
|
Killer Import Error: ORA-01426: numeric overflow
|
|
|
|
Numeric overflow on script for high date values
|
Numeric overflow on script for high date values
|
|
|
|
DateAdd 1st of month: Numeric overflow -- ERR #2 Line X
|
DateAdd 1st of month: Numeric overflow -- ERR #2 Line X
|
|
|
|
Reading Date/Time fields from a Mashupscript/Appscript may fail if the Date is before Jan 1, 1970 or past Jan 19, 2038
|
Accessing date/time fields from your Mashupscript/ Appscript either results in no result at all or in a " Numeric Overflow " error in the Windows Application Log.
|
|
|
|
AppScript SetFieldValue handles non English decimal separator incorrectly
|
Steps to reproduce: - in a process app add a numeric field with Fixed precision of 2 digits after decimal point (named BETRAG) - add the following code as AppScript:
|
|
|
|
AppScript locale issue - decimal point/comma separator gets removed
|
This is an issue with AppScript and how it handles decimal points for different locales (ie.“German ”) . Numeric fields using a locale where the decimal separator is a comma are saved correctly, retaining the comma separator. However, if the numeric field is used for calculations in an App Script, the comma is stripped and the number is processed as a whole number.
|
|
|
|
"Arithmetic overflow error" in report when calculating a SUM of summation field
|
Steps to reproduce are as follows in the sample database: (1) Create three new fields in the Change Request workflow - CODE (single selection field - add 3 codes), TIMESPENT ( numeric ) and then SUMMATION (Summation field on TIMESPENT). (2) Submit a number of items into this workflow putting values in the CODE and TIMESPENT fields.
|
|
|
SBM AppScript Reference
|
SBM database records can be identified by name or by a pair of numeric codes. The VarRecord Object is best used to represent these database records. For details, refer to Object Types [page 56].
|
|
|
|
SBM AppScript Reference
|
SBM database records can be identified by name or by a pair of numeric codes. The VarRecord Object is best used to represent these database records. For details, refer to Object Types [page 59].
|
|
|
