Skip to main content

Troubleshoot common data migration and permission errors in PeopleXD

Steps you can take to resolve common data migration and user permission errors in PeopleXD.

Written by James Pardy

You can resolve common errors in PeopleXD that relate to data migration and user permissions. Each section below covers one error and the steps to fix it.


Resolve the 'Invalid' error during data migration

The 'Invalid' error usually occurs because of issues with file structure or data formatting, rather than missing permissions. Follow these steps to troubleshoot it:

  1. Start with a minimal test: Populate the person file template with only one new starter record.

  2. Upload the file: Use the Data Migration widget to upload the test file.

  3. Review error messages: If errors appear, carefully review the error messages and amend the data accordingly.

  4. Use the latest template: Ensure you are using the most recent person file template available in the Data Migration widget.

  5. Validate field formats: Use the column helper provided with the template to confirm that each field adheres to the expected format and values.

These steps help isolate formatting issues and ensure the file complies with the required rules before you attempt a full upload.

🤓Tip: Use a single test record to check your file before you attempt a full upload.


Resolve the 'Get params' access denied error

If you see a 'Get params' access denied error, it is likely due to missing permissions. Follow these steps to resolve it:

  1. Enable the required menu option: Add the 'Get params' Web Services menu option (WS_PAYROLL_MENU.GET_PARAMS) to the users' Menu Profiles.

  2. Verify the configuration: Ensure the permission is correctly applied to the relevant profile.

Once this permission is added, the background call should complete successfully, and the error will no longer appear.


Summary

By following these troubleshooting steps, you can resolve common data migration and permission errors in PeopleXD. Always use the latest templates and make sure user permissions are correctly configured to avoid these issues.


​

Did this answer your question?