Choice Values Missing for Custom Application Field After Installation

[GaneshBendkule]

Hi Community,

I’m working on a custom scoped application, and I’ve encountered an issue related to choice values on a String field.

🔹 Scenario:
I have a custom String field called AC Status on the task table.

The field is created within the scope of my custom application.

I have added predefined choices for this field (via sys_choice), and they are visible and working correctly in my development/vendor instance.

These sys_choice records are captured in the application package.

🔹 Issue:
After submitting the app to the ServiceNow Store and installing it on the certification instance provided by ServiceNow:

The field AC Status appears correctly.

However, the associated choice values are missing.

🔍 What I’ve Checked:

All sys_choice records are correctly configured and set to the proper table (task) and element.

These sys_choice entries are linked to the correct application scope.

❓ My Questions:
Why are the sys_choice values being skipped during installation, even though they are included in the app package?

[M Iftikhar]

Hi @GaneshBendkule, 

It is due to an issue with how the ServiceNow platform handles sys_choice records for global tables, like the task table, when they are included in a scoped application. Even though the choices are captured in your application package, they can be skipped during the installation on a different instance.

You can manually export the sys_choice records as an XML or Excel file from your development instance and then import them into the target instance after the application has been installed. This ensures that the choices are created correctly.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.