Here’s a step-by-step approach to resolving this issue:
Check Field Type and Linked Records:
Ensure the User field is correctly set up as a linked record field pointing to the correct user table or base in WS-C.
Verify if the field is pulling from a cached list or an old record set.
Clear Field Options:
If the User field is set to allow multiple records, try clearing out any old or outdated user data from the field options. This might involve manually removing old entries or resetting the field configuration.
Reconfigure Field Settings:
Edit the User field settings in WS-C. You may need to reconfigure or refresh the settings to ensure that it only displays users with access to the current workspace.
Check for Linked Records:
Inspect if there are any linked records or references from WS-A that might be affecting the field. Sometimes, duplicated bases can retain links to old user records.
Refresh Workspace and User List:
Log out and log back into Airtable or refresh your browser to ensure you’re seeing the most up-to-date list of users and permissions.
Contact Airtable Support:
If the issue persists, it may be worth reaching out to Airtable support for a deeper investigation. Provide them with screenshots and details of the problem for more specific guidance.
Following these steps should help you address the issue of unexpected users appearing in your dropdown list.
That is indeed strange! If it's only appearing on the Kanban view I'd assume it's some sort of bug that needs to be reported.
If you want to utilize the Kanban view, I'd toggle on the "Hide Empty Stacks" option. Found at the bottom when choosing which field to stack by
Here’s a step-by-step approach to resolving this issue:
Check Field Type and Linked Records:
Ensure the User field is correctly set up as a linked record field pointing to the correct user table or base in WS-C.
Verify if the field is pulling from a cached list or an old record set.
Clear Field Options:
If the User field is set to allow multiple records, try clearing out any old or outdated user data from the field options. This might involve manually removing old entries or resetting the field configuration.
Reconfigure Field Settings:
Edit the User field settings in WS-C. You may need to reconfigure or refresh the settings to ensure that it only displays users with access to the current workspace.
Check for Linked Records:
Inspect if there are any linked records or references from WS-A that might be affecting the field. Sometimes, duplicated bases can retain links to old user records.
Refresh Workspace and User List:
Log out and log back into Airtable or refresh your browser to ensure you’re seeing the most up-to-date list of users and permissions.
Contact Airtable Support:
If the issue persists, it may be worth reaching out to Airtable support for a deeper investigation. Provide them with screenshots and details of the problem for more specific guidance.
Following these steps should help you address the issue of unexpected users appearing in your dropdown list.
There is no linked table to users either here, or in the original base. The original just listed possible users from those with access to it. It did not even have a field for users/assignees. That is something new for this version. When the original was duplicated and then moved to a separate workspace, those users were not granted access. I cannot update the field settings because they are not part of the field settings; they ONLY appear on the kanban view and yes, while I can hide all blank stacks there, it could be alarming for a client. Please see screenshot of User field options (neither of the two shadow users included there to be able to remove)
That is indeed strange! If it's only appearing on the Kanban view I'd assume it's some sort of bug that needs to be reported.
If you want to utilize the Kanban view, I'd toggle on the "Hide Empty Stacks" option. Found at the bottom when choosing which field to stack by
True, but discovering shadow users listed--even if they are not active--could be alarming to a client. I have the stacks hidden currently but would like a more permanent solution. Thanks Justin!
