Table is not extending from Service Order (sm_order), unable to publish application using an update set

[Mussie]

Hi Guys,

I have created an application using application template of Advanced Service Management (Applications —> New —> Start from a template —> Advanced Service Management) and this is working as expected. However, when I publish the application into an update set (Applications --> Publish to an update set) and commit this update set in another instance, I realized that this request table which was supposed to be extended from sm_order have only 7 fields. Please check the below screenshots:

Request table in the source instance

Request table in the source instance

I checked the following:

- Checked the number of application files in both the source and target instances. They aren't drastically different (574 files in source, 483 files in target)

- Checked the update set logs, there are no errors

Is there anything else I need to do? This is the third time I am trying and getting the same result.

Mussie

[Chuck Tomasi]

That smells like a bug! I don't have an instant answer for you at this point.

I recommend reaching out to customer support. I'll be interested to hear what they have to say.

HI Service Portal - ServiceNow

Contact Support | ServiceNow

[Mussie]

Sure, will do. I will make sure to update this post with the final out. Thanks a lot.

Mussie

[Mussie]

Update - Customer support suggested (see mail snippet below) that we should publish the application via repository instead of Update Set:

----------------------------------------------------------------------------------------------------------------------------------------------------

Please refer the following wiki for this

http://wiki.servicenow.com/index.php?title=Creating_Custom_Applications#gsc.tab=0

==>Update Sets Note: Avoid using update sets to install applications. Instead, use the application repository or the ServiceNow Store to install applications.

This is not a recommended practice to install an application via an update-set. You should only use Export XML option for backup/documentation purposes and scoped application should be installed from the Service Now repository/Store.

We have seen a lot of issues with respect to this and we are having nigh priority tickets to clean up the stale references for the customer so that they can install the same application from the repository after the installation via update-set failed.

Hope this explains. Please let me know if you have more questions.

----------------------------------------------------------------------------------------------------------------------------------------------------

Discussing this with the client and will update the post soon.

Mussie

[Chuck Tomasi]

You are correct. I should have noted that. Sorry. For scoped applications, publish/install is preferred to update sets.

[Mussie · Accepted solution]

Publishing the application to the repository have resolved my issue. For the benefit of others, I will least the steps I followed:

1. Go to System Applications--> Applications

2. Click Edit beside the application you want to publish (in my case 'Advancement'):

This will take you to Studio

3. Go to File --> Publish

4. Change the version to higher than the previous one (if published before), enter the Dev Notes if required the click Submit

5. Follow the progress bar and wait it completes

6. Once completed successfully, you should see the below page:

7. On the target instance, go to System Applications --> Applications --> Downloads tab

8. Click Install and wait till it completes

Thank you,

Mussie