The customer on that ticket creates nodes via requisitions, and their staff sometimes edit the asset-data categories (pollerCategory, notifyCategory, etc.) outside the requisition workflow. When the staff makes these changes via this workflow, the "userlastmodified" asset field gets updated automatically, and the customer has come to depend on this fact. The problem is that, when the node's requisition gets synchronized following one of these edits, the "userlastmodified" field gets zeroed out.
Can we special-case this field so that synchronizing the requisition will not clear this field (which is not directly settable in the requisition anyway)?
Environment
Any environment with nodes created via requisitions
This issue is in support of https://mynms.opennms.com/Ticket/Display.html?id=1983
The customer on that ticket creates nodes via requisitions, and their staff sometimes edit the asset-data categories (pollerCategory, notifyCategory, etc.) outside the requisition workflow. When the staff makes these changes via this workflow, the "userlastmodified" asset field gets updated automatically, and the customer has come to depend on this fact. The problem is that, when the node's requisition gets synchronized following one of these edits, the "userlastmodified" field gets zeroed out.
Can we special-case this field so that synchronizing the requisition will not clear this field (which is not directly settable in the requisition anyway)?