Decimal field weight in risk assessment

Davem89
Tera Contributor

Hello , when i try to change the decimal field "weight" in risk assessment  the field automatically updates the value x 100 anybody knows how to solve this?

6 REPLIES 6

@Davem89 

this field doesn't seem to be audited (unless enabled but I don't expect it was), which means that no changes are visible here but you can check following:

  • in the form that you shared
    • click the right mouse button on the Weight field,
    • select Configure Dictionary:

KamilTEL_0-1751797492352.png

 

There click right mouse button in the grey banner and copy the sys ID of this record:

KamilTEL_1-1751797674473.png

 

Then navigate to the table sys_update_xml, the screenshot doesn't display it in full:

KamilTEL_3-1751797740628.png

This table displays all the custom changes made to update set, and in the Payload search for "contains + the sys id":

KamilTEL_4-1751797832265.png

 

So if there is any customisation made against that the Weight field, it should be searchable here.

 

Not sure if this can help your problem, if it will not find anything in the Customer update [sys_update_xml] table, then we tried it. But if you will find there something it will mean that it has been touched and you can review the changes.

 

Otherwise I see no reason why the Weight field would have such strange behaviour. And in the worst case, you can create a HI Case for ServiceNow team to assist you, usually they respon very quickly.

Let me know if it helped a bit.

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


Mohammad Danis1
Giga Guru

Hi @Davem89 ,

It’s possible that a Business Rule, Script Include, or UI Script is responsible for multiplying these values automatically when you save the record.

Business Rule on risk_question or risk_assessment: Check if there are any before or after business rules that modify the weight or points fields before saving.

Example Business Rule:

javascript
Copy
Edit
if (current.weight) {
current.weight = current.weight * 100;
}
if (current.points) {
current.points = current.points * 100;
}
If you find this kind of script, it could be the cause of the problem.

Regards,
Mohammad Danish