Custom Fields Not Retained in Resource Assignment After Resource Allocation

Bindu16
Tera Contributor

We have added custom fields to the Resource Assignment (RA) table. As part of the standard process, the Project Manager creates an RA group, and upon submission, the Resource Manager assigns a resource to the RA.

When a resource is assigned, the out-of-the-box (OOB) functionality deletes the original RA record and creates a new one, automatically copying all standard (OOB) fields to the new RA record.

We now need to identify where in the platform the logic/script that handles this field copy resides, so we can extend it to also include our custom fields in the copy process.

Could you help us locate the script or logic responsible for copying the OOB fields during this RA recreation process?

 

Image: Before assigning a resource to the Resource Assignment (RA), the fields Technical Service, Offering, Managed by Group, and Manager had values populated.

2 REPLIES 2

Gaspar Fiks
Tera Expert

Hi @Bindu16 , have you ever find the script behind that logic ? Im having the same issue. 

 

Thanks! 

Arnab19
ServiceNow Employee
ServiceNow Employee

Hi,
If you are creating unassigned resource assignments(RA) and then assigning the resources, currently it deletes the original RA and creates new RA. We are changing this behaviour in Q4'2025 release. The existing RA won't get deleted.