Hi,
One of customized field values are not indication after the system upgrading in the system, which is a text customized field and the field name is UsrShipment_Num. other text customized fields are working without any errors which are same to the mentioned earlier.
Is the issue arised due to the underscore ( _ ) symbol?
what can I do for correct this issue?
Please advise on this
Thanks
Prasad
Best answer by jamesh
Hi
After reviewing the release notes for 2023 R1, significant changes were made that could potentially affect the visibility or functionality of your custom fields. Notably, the performance improvements involved moving more than 100 database columns from extension tables to their parent tables. These changes are significant because any customizations, reports, or Generic Inquiries that referenced the affected extension tables might need to be updated to reflect the new schema.
Since the database schema has changed, specifically with columns being moved from extension tables to their parent tables, you need to verify if the table or column where UsrShipment_Num is stored has been affected. Check if the field's table or its relations have been modified in the upgrade.
Any customization or Generic Inquiry that previously referenced moved or modified columns needs to be reviewed and potentially adjusted. This is crucial for ensuring that your custom field correctly references the new table structure. You’ll essentially want to make sure you’re referencing an existing DAC, or point it to a new one.
Given the extent of database schema changes, consider rebuilding indexes, especially if the system suggests that the search index may become outdated post-upgrade. This can help in improving the visibility and responsiveness of new and adjusted fields in queries and Generic Inquiries .
+7Hi
After reviewing the release notes for 2023 R1, significant changes were made that could potentially affect the visibility or functionality of your custom fields. Notably, the performance improvements involved moving more than 100 database columns from extension tables to their parent tables. These changes are significant because any customizations, reports, or Generic Inquiries that referenced the affected extension tables might need to be updated to reflect the new schema.
Since the database schema has changed, specifically with columns being moved from extension tables to their parent tables, you need to verify if the table or column where UsrShipment_Num is stored has been affected. Check if the field's table or its relations have been modified in the upgrade.
Any customization or Generic Inquiry that previously referenced moved or modified columns needs to be reviewed and potentially adjusted. This is crucial for ensuring that your custom field correctly references the new table structure. You’ll essentially want to make sure you’re referencing an existing DAC, or point it to a new one.
Given the extent of database schema changes, consider rebuilding indexes, especially if the system suggests that the search index may become outdated post-upgrade. This can help in improving the visibility and responsiveness of new and adjusted fields in queries and Generic Inquiries .
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
