ATF steps are not been migrated properly from one instance to another using Update setsIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } After migrating an ATF test from a source instance to a target instance via an update set, the test steps do not contain the variable values. E.g For a simple test step such as Impersonate Test Step, on the source instance, there is a value for the user being impersonated but on the target, there is no value, even though the user exists on both instances with the same sys_id. This KB does not apply to instances where the source and target do not have identical variables Based on our documentation, this should not be the case. Troubleshooting After your due diligence checking that the instances are similar, the first thing to inspect is the XML payload of the update set that is been transferred. To check this, open the update set, then the update record, and select Show XML On the XML, look for the sys_variable_value attribute. If this attribute has a value, you do not need to continue with this KB. If the attribute is empty, you can continue reading on.Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } It is expected that the sys_variable_value attribute should have a value in order to capture the variables so this attribute been empty is the issue. The next step is to check the dictionary record for table = sys_atf_step, column name = input, and confirm if 'serializer=com.glide.vars.VariableValueXMLSerializer' attribute is present.Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } If the attribute is not present, adding this attribute will resolve the issue. The Serializer attribute has read and write role set to maint, which prevents admins from editing this through the related list. Either do through a change (example change CHG6475723), or advise the customer to go to "Advanced" view and edit the attribute text instead.Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } In addition to adding this attribute, it is good to also check what other dictionary records require this attribute and do not have it. To do this, navigate to the sys_dictionary table and build a filter on Type = Glide Var. As at the time of this KB, there are 6 dictionary records of Type Glide Var. 5 belonging to sys_atf_* tables and 1 belonging to wf_activity table. All 6 dictionary records should have 'serializer=com.glide.vars.VariableValueXMLSerializer' attribute present. More dictionary records of type Glide Var may be aded in the future. You can advise the customer to add this and retest capturing their tests in an update set. It is worth mentioning that table columns do not only gets attributes from its sys_dicitonary record, but also gets attribute from the type record (sys_glide_object) that the column type belongs to. In this case, the inputs column belongs to type glide_var, so attributes to be used for the column are from both the sys_dictionary record of sys_atf_step's inputs column, and the record of glide_var type (sys_glide_object_c2a847d1c0a8016400e1397987c642ee).