Custom Field Missing in Update Set

[jmiskey]

I am working on a Service Portal project/workflow, so I started a new Update Set for it.  When I finished, I moved my Update Set to another environment to apply it there.  In testing, I ran into an error caused by the following issue.

I created a new custom user field in the Approver (sysapproval_approver) table.  For some reason, this new custom field was not picked up in my Update Set.  Why would that be?

I know with many tables, you can export the record to an XML file, and the import the XML file in another environment (to ensure that the record has the same sys_id across the environments).  Is there any way to do that with custom table fields?

Here is what my field looks like:

Thanks

[Sabrina10]

In my experience, just exporting the XML for the dictionary entry for a new field will not automatically create the field.

Typically, when there is a new field created, there are three entries created in your update set, one for the Dictionary entry, one for the field label and another for the Form Layout changes.   

I would recommend adding the Versions related list to the Dictionary form and see what update set your field was captured in. 

If it was captured in the default update set, it is probably best to delete the field, create a new update set and then create the field again with the exact same name.  Don't capture the deletion in the new update set.

If it was captured in a different update set, you may need to move that update to test or move the 3 entries I mentioned above to a new update set.

[Jaspal Singh]

Hi,

Can you check once if the field was captured in Update Set by looking in sys_update_xml table once. Alternatively, you try adding the Version related list to the update set form to see where it was captured. As, XML export import would lone not work till the time field is in place in target table.

Thanks,

Jaspal Singh

Hit Helpful or Correct on the impact of response.

[jmiskey]

I checked the sys_update_xml table and for some reason, this new field was put in the Default update set.  Not sure why, but I created a new update set and moved these record into it, exported that one, and imported it to my other environment and was able to successfully create it in that other environment.

Don't know why it happened, but at least I was able to fix it.

Thanks!