Skip to main content

How do I verify user update results and resolve errors?

Learn how to verify whether user updates were applied successfully in the Admin Portal and how to identify and resolve common update failures.

Written by Lauren Baird

Answer

After you submit a user update in the Admin Portal, you must review both the Successful Submissions and Failed Submissions results tables before leaving the page. A row in Successful Submissions only means the request was processed. It does not always mean the update was actually applied.

Always look for an errorType value in the returned rows. If an errorType appears, that user’s update failed, even if the row appears in Successful Submissions.

Use this process after:

  • in-line edits

  • Bulk Update Users

  • Bulk Update Division IDs

Also use it when users report access, workflow, or hierarchy issues after an update.


Steps

  1. Open ANVL Insights.

  2. Select Welcome, [Your Name].

  3. Select Admin Portal.

  4. Open User Management.

  5. Submit your user update.

  6. Wait for processing to complete.

  7. Scroll down to the results section.

  8. Review both:

    • Successful Submissions

    • Failed Submissions

  9. Check every returned row before navigating away from the page.

  10. Look specifically for any errorType value.

Successful Submissions

  • One row is returned per user.

  • This means the request was processed.

  • It does not guarantee the update was applied.

  • If the row includes an errorType, the update failed for that user.

Failed Submissions

  • These rows did not update successfully.

  • Common causes include:

    • invalid data format

    • incorrect field values

    • missing required fields

    • relationship or hierarchy conflicts

Common failure: Supervisor and Group mismatch

A common rule that causes failures is:

  • a Supervisor must belong to all Groups that their direct report belongs to

This failure usually happens when:

  • a user is moved to a different Group

  • the user already has a Supervisor

  • that Supervisor is not assigned to the new Group

When that happens:

  • the update fails for that user

  • an error appears in the results table

How to resolve supervisor-related failures

Option 1: Correct the Supervisor’s Group membership

  1. Review the Supervisor’s assigned Groups.

  2. Confirm the Supervisor belongs to every Group assigned to the user.

  3. Re-submit the update.

This is usually the best option for bulk updates.

Option 2: Clear and reassign the Supervisor

  1. Remove the current Supervisor assignment.

  2. Save and confirm the user update succeeds.

  3. Verify the intended Supervisor belongs to all required Groups.

  4. Reassign the Supervisor.

This is usually easier for one-off fixes.

When to use ANVL Insights instead

  • If you are fixing a single user, it may be easier to make the change in ANVL Insights from the Users tab instead of re-running a bulk update.

What to do before leaving the page

  1. Confirm there are no unresolved rows with an errorType.

  2. Correct and re-submit failed updates as needed.

  3. Refresh and verify the final user state if the update affects access, supervisors, or Groups.

Important notes

  • Do not assume an update worked just because it appeared in Successful Submissions.

  • Always review both result tables.

  • Hierarchy and Group relationship issues are a common reason updates fail.

  • Misreading the results can leave users with the wrong access, wrong supervisor, or broken visibility.


Did this answer your question?