Deprecation of Users and Organizational Unit (OU) Loads and Feeds for Data Load Wizard (DLW) with the May '22 Release
Ability to perform Users and OU data loads and feeds using Data Load Wizard (DLW) will be deprecated with an end-of-life in the May ‘22 Release. End-of-support will occur in the February ‘22 Release and support for defects related to DLW Users and OU loads and feeds will stop at this time.
DLW is a legacy data load tool which was built on older technology, is accessed using an outdated user interface (UI), and experiences slow performance and limited load type support. Edge Import addresses these issues with a modern UI and an intuitive workflow that can support a greater number of concurrent loads, while providing administrators with a delightful user experience.
Existing customers who are ready to migrate to Edge Import will be able to enable Edge Import: Core on Edge Marketplace and review the migration and starter guides to help them through the migration steps. All customers are required to complete their migrations before the May ‘22 release which will be the end-of-life date for DLW Users and OU loads and feeds.
Important: For customers in one of the following scenarios, we do not recommend migration of Inbound Data Feed (IDF) for Users and OUs from Data Load Wizard to Edge Import at this time:
- Customers using Data Load Wizard Group OU loads.
- Customers using Cornerstone Recruiting who also use Cornerstone's Applicant Conversion feature.
- Customers using GUID as You are a Customer using GUID for purpose of Userid changes AND loading Userid relationships in the same file (ManagerID, ApproverID, Custom Employee Relationshp ID), not for applicant conversion.
An additional enhancement is planned for Edge Import that will support this functionality. Once this enhancement is released, there will then be a three-month period to allow for migration for these customers.
If your portal uses Cornerstone Recruiting, GUID in Data Load Wizard loads and feeds, or has Group OU data loads, you will be automatically excluded from the migration in May. If your portal does not match these scenarios but this migration impacts you, please log a case via Support Central to request an extension to the migration and deprecation date with the May ’22 release.