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
Updated over a week ago

User updates in the Admin Portal apply to live accounts. Even when a submission appears successful, individual user rows may still fail. Misinterpreting results can leave users incorrectly configured and cause access, assignment, or hierarchy issues.

Use this process after submitting:

  • Inline edits

  • Bulk Update Users

  • Bulk Update Division IDs

Also use it when users report access or workflow issues after updates.


Answer

After saving user updates in the Admin Portal, you must review both the Successful Submissions and Failed Submissions tables. Always check for errorType indicators—even within Successful Submissions—to confirm whether updates actually applied.


Steps

  1. Save your update from the User Management tab in the Admin Portal.

  2. Wait for processing to complete.

  3. Scroll down to locate the results section.

  4. Review both tables carefully:

    • Successful Submissions

    • Failed Submissions

  5. Validate each returned row before navigating away from the page.

Do not assume changes were applied without reviewing both sections.


Interpreting the Results

Successful Submissions

  • One row is returned per user.

  • This means the request was processed—not guaranteed applied.

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

Always scan for errorType, even in the Successful table.

Bulk update results showing successful submissions and failed submissions; any row with an errorType indicates the update failed for that user, even if in the Successful Submissions table.


Failed Submissions

  • The update was not applied

  • Common causes include:

    • Invalid data format

    • Incorrect field values

    • Missing required fields

These rows must be corrected before re-submitting.


Common Failure Scenario: Supervisor & Group Mismatch

Rule

A Supervisor must belong to all Groups that their direct report belongs to.

If this rule is violated, the update fails.

What Causes the Failure

  • A user is moved to a different Group

  • The user already has a Supervisor assigned

  • The Supervisor is not a member of the new Group

Result

  • The update fails for that user

  • An error message appears in the results table


How to Resolve Supervisor-Related Failures

Option 1: Correct Group Membership (Best for Bulk Updates)

  1. Verify the Supervisor’s Group membership.

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

  3. Re-submit the update.


Option 2: Clear and Reassign the Supervisor (Best for One-Off Fixes)

  1. Remove the Supervisor assignment.

  2. Save and confirm the update succeeds.

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

  4. Reassign the Supervisor.

Tip: For single-user fixes, it may be easier to perform changes in the Users tab (ANVL Insights) instead of using bulk updates.


Additional Details

Job Role: Business Administrator | Permission Level: Admin / ANVL Web | Special Rights: Admin Portal

Did this answer your question?