Could not find a table field - update set error (but the field exists)

Staxed · ‎03-06-2022

I am trying to apply an update set but I am getting 6 "Could not find a table field referenced in this update" errors.

However, when I look at the table, these fields do indeed exist. Is it safe to just go ahead and accept these remote updates in this case, or is there something else I should be looking at...not sure why it's producing these errors when the fields exist.

DrewW · ‎03-06-2022

Ok, Have you looked at the XML of the update to see what table and field they are to make sure you are looking at the right ones?

Ultimately committing the update is not really going to hurt anything. Just check the form when you are done and make sure everything is there and in the right places.

View solution in original post

ersureshbe · ‎03-06-2022

Hi,

Is that field available in source instance not in destination instance ie which instance you are going to commit the update set?

If yes, may the field creation captured in different update set then create another update set and capture the field from the table .

First you should commit this update set and finally move update set which throws an error. I'm not sure how you are moving the update set from one instance to another.

I would recommend to use remote instance option from OOB functionality and move the code.

Regards,

Suresh.

Regards,
Suresh.