Set Values could not determine the record to update as it is in different Application scope.
Release or Environment
Madrid Patch 5
This can be achieved in two ways:
1) Enable System Property: glide.record.legacy_cross_scope_access_policy_in_script
The purpose of the System Property is:
Legacy behavior provided create/update access to tables that did not allow so. In order to prevent legacy customers from having applications broken when this behavior was patched we created the 'glide.record.legacy_cross_scope_access_policy_in_script' GlideProperty which, when true, causes this function to fall back on legacy behavior.
2) Check the Table configuration of 'Custom Table'
Here in the Application Access section, Can Read, Can create and Can update should all be checked.