- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2022 08:15 PM
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
Solved! Go to Solution.
- Labels:
-
Scoped App Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2022 08:45 PM
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
Regards,
Shloke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2022 08:24 PM
Hi,
Please see suggestion below which you need to follow:
1) I believe you can accept those error as these are because of below reason:
"That catalog item category is not present on your target instance.
Make sure that you export XML of this category from source to destination and then run update set preview again."
You need to do the same thing for both Number and Category. Accept the warning or errors and then once update set is committed manually move the export of these two XML into your Target instance.
Hope this helps. Please mark the answer as correct/helpful based on impact.
Regards,
Shloke
Regards,
Shloke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2022 08:31 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2022 08:45 PM
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
Regards,
Shloke
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2022 08:48 PM
For your second issue, please check the below setting in your target instance as mentioned below:
"Also, for importing of the XML for the numbering there is an issue:"
On your Target instance, Navigate to your Number Maintenance table and then check for below settings, it should be Accessible to All Applications as shown below:
Make sure the check boxes are marked as True:
Hope this helps. Please mark the answer as correct/helpful based on impact.
Regards,
Shloke
Regards,
Shloke