Field visible in the Dev and QA but not visible in the Prod instance

Vinod S Patil · ‎08-31-2023

Hello Everyone,

I don't see "mid server attachment" field in export set in Prod instance but same field visible in the Dev and QA instance.
what could be the reason, please suggest me.

Regards
Vinod

Harish Bainsla · ‎08-31-2023

Hi I think there are several reasons you have to check these

Configuration Difference: There might be a difference in the configuration of the instances. Check if there are any customizations, updates, or changes in the Production instance that might have caused this field to be hidden or removed from the export set.
Data Dictionary Configuration: Verify if the field's visibility is controlled by the Data Dictionary settings. If the field is marked as "Internal" or "Hidden" in the Production instance, it won't be included in the export set.
Update Sets: Check if there are any active or completed update sets in the Production instance that might have affected this field. An update set might have modified the visibility of the field, causing it to not appear in the export set.
Instance Versions: If your instances have different versions (e.g., a different ServiceNow release or patch level), there might be differences in the available fields and configurations.
Permissions and Roles: Verify if the user or role executing the export in the Production instance has the necessary permissions to access and export the "mid server attachment" field. Permissions might be different between instances.
Custom Scripting: If there's any custom scripting or business rules in the Production instance related to attachments, it might impact the visibility or exportability of this field.
System Property Settings: Certain system properties can control the visibility of certain fields. Check if any system properties are set differently in the Production instance that might affect this behaviorIf you get answer please mark helpful and accept solution

View solution in original post

Harish Bainsla · ‎08-31-2023

Hi I think there are several reasons you have to check these

Configuration Difference: There might be a difference in the configuration of the instances. Check if there are any customizations, updates, or changes in the Production instance that might have caused this field to be hidden or removed from the export set.
Data Dictionary Configuration: Verify if the field's visibility is controlled by the Data Dictionary settings. If the field is marked as "Internal" or "Hidden" in the Production instance, it won't be included in the export set.
Update Sets: Check if there are any active or completed update sets in the Production instance that might have affected this field. An update set might have modified the visibility of the field, causing it to not appear in the export set.
Instance Versions: If your instances have different versions (e.g., a different ServiceNow release or patch level), there might be differences in the available fields and configurations.
Permissions and Roles: Verify if the user or role executing the export in the Production instance has the necessary permissions to access and export the "mid server attachment" field. Permissions might be different between instances.
Custom Scripting: If there's any custom scripting or business rules in the Production instance related to attachments, it might impact the visibility or exportability of this field.
System Property Settings: Certain system properties can control the visibility of certain fields. Check if any system properties are set differently in the Production instance that might affect this behaviorIf you get answer please mark helpful and accept solution