Available on Test for all regions on 12 May and 19 May on Production
Object management improvements
Improved performance and usability when working with objects that have a large number of relations
- Relation lists now use infinite scrolling, making large datasets load faster and improving the overall user experience.
- Changes to relations are now handled in a deferred save flow:
- Added or removed relations remain in a pending state until you click Save
- Discarding changes restores the previous state instantly without reloading data
- These improvements apply only to relation lists on the main object. Memberships, other related entities, and availability related fields are unchanged
- Updated export behavior to improve consistency and readability
Export columns now follow this order:
- Ext. ID
- TE Internal ID
- Field data
- Object type
- Associations
- General info
Export error handling has been improved for large datasets
- Users now receive a clearer error message when an .xlsx export exceeds Excel cell size limitations
- The message explains that the .xlsx format cannot handle the data size
- Users are guided to retry the export using .csv format instead
Columns saved
- When a user selects or deselects columns for each object type, the configuration is now saved in localStorage
- When the page is refreshed, the previously selected columns remain visible
Result CSV files are now easier to review with improved sorting behavior
- Export results are now primarily sorted by status and secondarily by external ID
- Rows are displayed in the following order:
- Error
- Unchanged
- Success
Updated UI authorization configuration
Applicable only for users with this permission
Auth configs are now in tabs instead of sidepanel
- Select to choose auth config
Copy auth config and delete auth config are now larger buttons
- Copying will create new tab with prefix “[COPY]“
Bug fixes
Fixed an issue where exporting objects to .xlsx could fail with the error: "Cannot read properties of undefined (reading 'find')"
- The issue could occur when exporting filtered objects together with availability-related and relation attributes from Object Manager