Forum Discussion
MS List suddenly not displaying (or saving) multiple selections from column
It’s quite an interesting issue. I’ve never experienced this behavior myself. But here are a few troubleshooting steps you can try, in case you haven’t already explored them:
1. Confirm whether the data is actually being saved
Open the item in Edit mode (click on Edit all) and check the lookup field.
- If only one value appears: the issue is with saving
- If all values appear: the issue is with display/rendering
This helps narrow down the root cause.
2. Check if the source list has unique permissions
If the lookup source list or individual items have restricted permissions, SharePoint can sometimes fail to save multiple lookup values correctly.
3. Edit a property to refresh the lookup column schema: You can try updating the original lookup column (for example, add a description, save it, then remove the description and save again). This sometimes forces SharePoint to refresh the column schema and resolve the issue.
If that doesn’t help, re‑creating the column is the most reliable fix.
✔️ [Toggling the ‘Allow multiple values’ setting resolved the problem]
Temporarily turning off Allow multiple values and then turning it back on can force SharePoint to refresh the internal schema for a lookup column.
Steps:
1) Edit the lookup column
2) Uncheck Allow multiple values
3) Save
4) Re‑open the column settings
5) Turn Allow multiple values back on
6) Save again
This forces SharePoint to rebuild the field definition, which often fixes situations where multi‑value selections stop saving correctly.
⚠️ IMPORTANT NOTES (Data‑loss warning)
This workaround does carry a data‑loss risk.
When you toggle Allow multiple values, SharePoint rewrites the internal field schema and drops all but the first stored value for every existing item. If your list already contains valid multi‑value data, make sure to back it up or export it before using this workaround.
4. Try creating a brand‑new lookup column
This is the quickest way to confirm whether the issue is with the column itself.
Create a new test column with:
- Lookup > same source list
- Allow multiple values > Yes
Then try saving multiple selections.
If the new column works: The original column is likely corrupted. Re‑create it and migrate the data to the new column.
If my post solved your issue or answered your query, please mark it as a Solution and give it a Like.
It’s quite an interesting issue. I’ve never experienced this behavior myself. But here are a few troubleshooting steps you can try, in case you haven’t already explored them:
1. Confirm whether the data is actually being saved
Open the item in Edit mode (click on Edit all) and check the lookup field.
- If only one value appears: the issue is with saving
- If all values appear: the issue is with display/rendering
This helps narrow down the root cause.
2. Check if the source list has unique permissions
If the lookup source list or individual items have restricted permissions, SharePoint can sometimes fail to save multiple lookup values correctly.
3. Edit a property to refresh the lookup column schema: You can try updating the original lookup column (for example, add a description, save it, then remove the description and save again). This sometimes forces SharePoint to refresh the column schema and resolve the issue.
If that doesn’t help, re‑creating the column is the most reliable fix.
✔️ [Toggling the ‘Allow multiple values’ setting resolved the problem]
Temporarily turning off Allow multiple values and then turning it back on can force SharePoint to refresh the internal schema for a lookup column.
Steps:
1) Edit the lookup column
2) Uncheck Allow multiple values
3) Save
4) Re‑open the column settings
5) Turn Allow multiple values back on
6) Save again
This forces SharePoint to rebuild the field definition, which often fixes situations where multi‑value selections stop saving correctly.
⚠️ IMPORTANT NOTES (Data‑loss warning)
This workaround does carry a data‑loss risk.
When you toggle Allow multiple values, SharePoint rewrites the internal field schema and drops all but the first stored value for every existing item. If your list already contains valid multi‑value data, make sure to back it up or export it before using this workaround.
4. Try creating a brand‑new lookup column
This is the quickest way to confirm whether the issue is with the column itself.
Create a new test column with:
- Lookup > same source list
- Allow multiple values > Yes
Then try saving multiple selections.
If the new column works: The original column is likely corrupted. Re‑create it and migrate the data to the new column.
If my post solved your issue or answered your query, please mark it as a Solution and give it a Like.
Thank you VERY MUCH for your detailed and actionable suggestions, sir.
Referencing them in order:
I discovered, unfortunately, that the expected values did not appear in Edit mode, thus the problem was with saving.
I double-checked the permissions to the source list, and the users of the target list have read access to the source list, so this does not appear to be the problem.
Editing the properties of the list did not fix the problem.
Creating a new lookup column DID correctly allow saving multiple selections
That being the case, is migrating the data from the existing to new column as simple as copy/pasting from one to the other, or is there a better way to do it?
More importantly-- and I thought I would ask since you clearly know the product fairly well (and certainly far better than I do) is there any way to know how this corruption occurred and how to prevent it from happening again?
For example, is there something inherently problematic about multiple selections in Lookup columns as opposed to say, a choice column? When making this list, I chose the former because the list of employees frequently changes, so I thought it would make more sense to keep that in its own list rather than constantly having to add/remove options in a choice column.
But now I wonder if that's a reliable way to approach it. As things stand, data that's been collected has been lost as a result of this issue, and I've got a feeling I could easily find myself in the same situation in a week, a month, or a year. Would really like to avoid that if at all possible.
Again, very much appreciate your help!
Thanks for the updates.
Could you please try one more option? Last time I suggested updating the Description property, but since you mentioned that the field is saving only one value, let’s try this:
Temporarily turn off “Allow multiple values” Uncheck Allow multiple values, save the column, then turn it back on and save again. Sometimes this forces SharePoint to refresh the field schema.
If this also doesn’t work, then yes creating a new column is the only reliable fix.
Regarding whether to use Choice, Lookup, or Managed Metadata: How many values do you have in the employee list?
- If the list is small (around 20 or fewer), Managed Metadata is a good option.
- If the list is large, Lookup is still appropriate.
For copying/migrating values, you can use:- PowerShell (Custom Script)
- Power Automate (Build automate to perform this task)
Both can read values from the old column and update the new one.
OK, that actually did the trick. By turning off "allow multiple selections" and turning it back on again, the original column is now saving multiple values.
That's great since it saves me from creating a new column, exporting data, etc. But as far as you know is there any way to find out what caused or prevent the corruption? Given past experience it seems certain that this will happen again at some point, and since there is no warning it may be a while before someone notices.
Regarding my list it's just under 100 names so I guess I am stuck with a lookup column.
Incidentally, as part of my troubleshooting I consulted CoPilot for Business in browser session with the affected list open, and it referenced a "multii-value lookup bug".
Quoting copilot here:
Here’s why your situation fits it perfectly:
- You’re using the default modern form
- The lookup column allows multiple values
- The source column is Title (single line of text) — the ideal type
- You have only one lookup column in the list
- The form is not customized with Power Apps
- You’re selecting multiple values, but only one (or none) saves
This is the exact pattern of the regression that started rolling out in late 2024 and continued through 2025–2026. Microsoft Lists and SharePoint Online introduced a bug where:
- Multi‑select lookup fields render correctly
- The picker allows multiple selections
- The form silently fails to save more than one value
That certainly sounds plausible, but I haven't found anything online that corroborates it.
Unfortunately, the solution it offered, switching the form to the classic experience, was not an option available to me.
