You design the data migration process.
The legacy data records have ownership problems.
For some records, the ownership column is empty.
For others - store owners that are no longer with the company.
Please select three methods you can use to correct this problem.
Click on the arrows to vote for the correct answer
A. B. C. D. E.Correct Answers: A, B and.
D.
When a Solution Architect designs the data migration, he or she needs to consider several things, like compliance, lack of documentation for the legacy systems and data, data duplication, required columns are empty, no unique record identifiers, no established relationships between tables, missing ownership of the records, etc.
The Dataverse requires record ownership.
If the legacy data cannot provide this information, you need to work with stakeholders to solve this problem.
There are three methods: Use a predefined user - the stakeholders can provide a user, fully registered in the Dataverse, that will be used in case of missing values or for all the records.
Use a stub user - this is a user who does not have a Dataverse login or data access but can be used only to import the legacy data into the Dataverse and preserve the original record owners.
You can use this user type only for Excel-based import.
Use a service identity - the identity should be provisioned in the Dataverse and have all the security rights to write data to all Dataverse tables and perform the API calls.
This identity will own all the records without a specific owner.
All other options are incorrect.
For more information about the data migration planning, please visit the below URLs:
Sure, I can explain the different methods you can use to correct the ownership problem in the legacy data records during the data migration process.
Use Stub Users: One method to correct ownership problems in legacy data records is to use stub users. Stub users are temporary users that are created solely for the purpose of migrating data. You can create a stub user with a generic name such as "Unknown" or "Unassigned" and assign it to records where the ownership column is empty or where the store owners are no longer with the company. This ensures that all records have an owner and prevents any issues with data integrity.
Use Service Identity: Another method to correct ownership problems is to use service identity. You can create a service account or a system-managed identity for your migration process and assign it as the owner of records with ownership problems. This method ensures that ownership is consistent across all records and eliminates the need to create and manage stub users.
Use Predefined User: You can also use a predefined user to correct ownership problems. A predefined user is a user account that already exists in the system and can be used to assign ownership to records during the migration process. This method requires that you identify a user account that can be used as the default owner for records with ownership problems. It also requires that you ensure that the predefined user has the necessary permissions to access and modify the records.
Note: Using an empty column or skipping the column and provision a new column after migration are not viable methods to correct ownership problems in legacy data records. An empty column does not provide any ownership information, while skipping the column and provision a new column after migration can lead to data integrity issues and inconsistencies.