Field shows updated in history but not on form

kristenankeny
Tera Guru

I have seen a couple instances in our system where a field shows updated in the audit history (and in the activity history when dealing with Requests), but not updated on the form.

This is one example - the form shows the state In use:

find_real_file.png

However, when I look at the audit history, I can see that it was changed to Retired:

find_real_file.png

Why is this not reflected on the form?

I checked:

The State on the form and the State in the audit history are the same field

The State column has a choice for "Retired" for the table (alm_hardware)

That Retired and In Use have different values

1 ACCEPTED SOLUTION

kristenankeny
Tera Guru

We found the source of the issue. We have the "Add to update set" UI action installed from Share. When making some changes for a project, we updated records in dev and moved them up to production. Those overwrite the production updates, but didn't record any changes in the audit history, which is why it looked like nobody had updated it and the audit history and record don't match.


View solution in original post

4 REPLIES 4

randrews
Tera Guru

is Retired a valid choice on the choice list for that item?   if it is not it SHOULD show the value in blue letters .. . however if the option isn't even in the choice list.. that may preset an issue to showing it on the form.


Yes, it's a valid choice for the field.


abhishekdash
ServiceNow Employee
ServiceNow Employee

Hello Kristen,



Can you please open the record and right click on the header and click 'Show XML'.


Check the corresponding value for 'state' and compare if it's In 'Use' or 'Retired'.



My doubt is that the value is correct in the database but you might be having a client side script which is changing the value on form load.



Let me know how it goes.



Thanks,


Abhishek



If this reply assisted you, please consider marking it Correct, Helpful, or Like it.


This helps other customers to learn from your thread.


kristenankeny
Tera Guru

We found the source of the issue. We have the "Add to update set" UI action installed from Share. When making some changes for a project, we updated records in dev and moved them up to production. Those overwrite the production updates, but didn't record any changes in the audit history, which is why it looked like nobody had updated it and the audit history and record don't match.