Custom scoped app release to UAT issue

Rahman3 · ‎02-17-2022

Hi All,

We have created a custom scoped App where the tables are inherited from the Task table. And we have couple of issues releasing into UAT.

1) We have created custom numbering in the number maintenance module. However, when previewing the update-set (sanity testing) it complains that the "Could not find a record in sys_number for column number_ref referenced in this update". It basically cannot find these numbers in the update-set? We tried to create XML import files for the numbers from sys_number so we can import them in UAT but that is also not working. Can anyone please explain why is this and what is the best practice here?

2) The second issue is that it is complaining about "Could not find a record in sys_app_category for column category referenced in this update". I can see in the update-set that is referencing the "Custom Applications" and it definitely exists in the sys_app_category in the UAT. Why this error should happen?

TIA

shloke04 · ‎02-17-2022

Hi,

First error which you are getting is because of the Category value missing which is linked to the Application menu which you might have created for your Custom Application.

See screenshot below when we create a Application menu it check with us for the category as well as shown below:

So this category value you might have selected as Custom Application in your source instance which is not present in your Target instance.

In order to resolve this, navigate to the table "sys_app_category.LIST" from Application navigator as shown below:

Hit enter on the keyboard and then once the list open Right click on the header and then click Export-XML as shown below:

Now go to your Target instance and click on the module Retrieved Update set and then click on Import XML and import this XML which you have exported and then preview your Update set , error will be gone.

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

View solution in original post

shloke04 · ‎02-17-2022

Hi,

If you have a follow up query, please let me know else if my answer has helped you that please amrk my answer as correct and close this thread for others.

Regards,

Shloke

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

shloke04 · ‎02-17-2022

Hi,

If you have a follow up query, please let me know else if my answer has helped you that please amrk my answer as correct and close this thread for others.

Regards,

Shloke

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

Rosemary4 · ‎06-28-2022

I had the same problem as you for issue 2 - I hadn't specified a Category in the Application Menu, it was defaulting to Custom Applications in the XML, and the Custom Applications Category had identical name and sysID in both Source and Target environments.

I selected "Accept remote update" and the application was imported with no problems. Seems like a bug.