5 June 2026
Portal management
Custom user data: changes from String to String Choice types work correctly Issue resolved
For custom user data, you can change your field types from String, aka a field that accepts alphanumeric text entries, to String Choice, aka a drop-down field where the choices are predefined. Typically you make this change to make your data more consistent.
A customer reported that changing this field type made all the dropdown options blank.
The team reviewed the issue and resolved it. The dropdown entries appear, and any fields that do not have an equivalent entry from the dropdown list appear blank.
When no matching entry exists, the field stays blank, rather than retaining data that doesn’t appear in the dropdown list.
Reviewing your users' custom data before changing the field type can help you identify any potential blank entries.
See:
Bulk actions: the portal action tracker now provides clear messages for bulk engine results Enhancement Better messaging
For tasks with large volumes of data, LearnUpon uses its bulk engine. The bulk engine runs in the background on tasks like uploading large numbers of learners, or updating multiple content files at once. Typically an admin starts the task and moves on to work eslewhere in the application.
Within LearnUpon these tasks are called bulk actions.
After you start a bulk action, you can view its progress through the portal action tracker.
The team updated some statuses to make them clearer, and to make sure admins always received a completion status when a bulk action ended.
These statuses advise admins about their next steps. For example: for tasks that completed with errors or failed, they can download a report to identify what to change and run again.
See Portal: follow bulk actions through the portal action tracker
Bulk actions: undo a migration of training history with help from LearnUpon Enhancement
As part of routine development, the team have expanded the capacity of the bulk engine.
The bulk engine can now roll back migration histories, when required, within 7 days of the original migration.
To undo a migration, contact your Implementation Consultant or the Support team.
See Migration guide: moving your enrollment histories to LearnUpon