I might not know the actual issue. If you can post it on apex.oracle.com, it will be easier to debug.
Another quick resolution if you need, you can continue using disabled item on front end, but at back end, sum the initial items again to process the results.
Hope it helps.
Can you please explain what method you used to disable the item and how you are populate the total to that item??
what APEX version you are using???
Iam using apex 4.2 version and Iam populating the total and disabling the same by using a dynamic action.
What database version are you on?
If you are on 11g+, you should be using a Virtual Column instead.
1 person found this helpful
Disabled items do not get submitted per html specs. This means submitting a page will not have a value to set in the session state of that item. And so your total is not set on the server-side. If you need it at the server-side, remove the disabled attribute before submit, make the item read-only instead (not editable by user but will submit), or do the calculation again (eg computation).
Got your point. Tried enabling the field before submit, but it is not reflecting the correct value in the back-end. Is there anyway to make the field a read-only field.?
Thanks in advance.
Are you tried to make the item read-only?? Make the item read-only and try. You can make the item read-only by two following methods,
1) Edit the Item-> Go to Read Only tab-> Read Only Condition Type: Always
make the item read-only instead (not editable by user but will submit)
Assign the total value to the item using DA. No need to enable the item before submit because the item is not disabled. Make the item as read-only so that it will submit the value to the session and item will not be editable always.