Details
-
Bug
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
CP: Sprint 145, CP Sprint 146
-
1
-
Core: Platform
-
Morning Glory (R2 2022) Bug Fix
-
TBD
Description
Overview:
When comparing module schemas between Bugfest MG and a new MG deployment, several schemas have differences in their x_set_md and set_x_md_json functions. These functions have differences in the way the date formatting is done for object metadata. This appears to affect all functions of the form x_set_md and set_x_md_json.
I've attached a set of screenshots showing an example from mod-audit. The full list of modules affected is:
- mod-audit
- mod-circulation-storage
- mod-data-import
- mod-data-import-converter-storage
- mod-email
- mod-erm-usage
- mod-event-config
- mod-feesfines
- mod-finance-storage
- mod-inventory-storage
- mod-invoice-storage
- mod-login
- mod-orders-storage
- mod-organizations-storage
- mod-permissions
- mod-users
TestRail: Results
Attachments
Issue Links
- relates to
-
MODINVSTOR-935 Schema differences between MG Bugfest and clean MG deployment: mod-inventory-storage
-
- Closed
-
-
RMB-759 Consistent format for createdDate and updatedDate metadata (breaking change)
-
- Closed
-
-
VERTXLIB-27 Release 2.0.1
-
- Closed
-