on 01-28-2015 4:49 PM
Hi all,
We use Work Manager 6.1 with some enhancements.
In an enhancement we have add a decimal field with precision 1.
On an android device (Samsung S4) it displays 0.0 as initial value. That's correct.
I fill in 60.1 (So in reality it displays 0.060.1). Still no problem, all correct.
As soon as this field loose focus and gain focus again the application put's 0.0 after the value, so the value becomes 600.1
What could be the problem?
regards,
P. Willems
In SAP Work Manager 6.1 (Designed in Agentry) when you specify a Decimal field that corresponds to a data type Decimal values, the numbers are X.Y. Where X is the decimal number before the period and Y is the number after the period.
When you have stated that the initial value is specified to be 0.0. That means the decimal number = 0.0 before data entry. When you fill in 60.1 (after data entry) the property of decimal with precision one should equal 60.1.
I am trying to understand if you have some values or update rules that concatenate the initial value + field value to equal 0.060.1.
When you lose focus this rule may be doing something that could cause 600.1.
From an Agentry perspective decimal number is a data type and it will always be a number with a decimal number in it (with the defined precision - 1 decimal, 2 decimal, etc.)
Your issue seems to be rule based. Was this field highly customized with rules?
Regards,
Mark Pe
SAP Senior Support Engineer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.