RITM | OnChange client script from Requested for OOB field

Nuno Oliveira · ‎04-14-2023

Hi there,

I have this requirement to change the location from a requested item when the requested for changes and I have created a on change client script with the requested for field as a trigger, however it doesn't work, don't even run.

And I noticed that the OOB field is a dot-walking field, so probably this is the cause of that isn't working.

Do you any idea how I can achieve this? With changing the field

Thanks in advance.

Best regards

Anil Lande · ‎04-14-2023

Hi,

After Paris release the 'Requested For ' field ins introduced on RITM.

Please check in List view and if it in synch with REQ.Requested_For value then you can add it on form.

Your client script will not work on RITM as the existing field is dot walked. Also it is not best practice to change value of dot walked field, it results in updating parent record.

Please appreciate the efforts of community contributors by marking appropriate response as correct answer and helpful, this may help other community users to follow correct solution in future.
Thanks
Anil Lande

Nuno Oliveira · ‎04-14-2023

Hey Anil,

Thank you.

Yes, I have noticed that field already, however we have another client scripts running on that form that could impact if we switch the OOB field for the new field.

That why I was asking if there is a way to achieve this without removing the field.

Mehta · ‎04-14-2023

The requested for on your form must the one being dot walked from request table. we do have another requested for on requested item table. you have to change form layout and bring the requested item table field instead of dot walked. Because you were making changes to requested for which is being dot walked there is nit triggering happening to your client script.

It seems your client script must have condition where requested for should get changed to trigger on change client script since it is not present on the form the trigging is not happening therefore you cannot see any action taken place by client script.

Nuno Oliveira · ‎04-14-2023

Hey Mehta,

Thank you.

As I said to Anil, we have another client scripts running in that form and switching the OOB field for the other one can impact the behaviour of those client scripts. So removing or hide that field isn't an option.