Share via

Bug in SharePoint Online's New Interface

Anonymous
2018-01-08T23:09:21+00:00

This is an issue we've only just noticed in using the new SharePoint Online interface. We use a managed metadata field/column that is linked to a closed term set and have this set as optional. This means that users can choose tags from a dropdown or leave it blank.

In the classic interface, there are no issues with removing tags from that column/field and leaving it blank, but when attempting to do so with the new interface, an error is shown to indicate that it is 'required' despite being an optional field.

The problem only occurs when a tag has been applied and a user attempts to remove the tag so that it becomes blank again.

Microsoft 365 and Office | SharePoint | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2018-01-17T00:18:22+00:00

    Hi Brent,

    Thanks for your reply in PM. After my test, I can't fix this error. Since you said you can creared a new normally list, I'd like to suggest you recreated this list. Appreciate your understanding.

    Regards,

    Neo

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-10T12:12:54+00:00

    Hi Brent,

    I didn't find this error message during my test.

    Please create a new list that also with metadata column then see the outcome.

    If this issue still exists, please share with me more details about it:

    1. The detailed steps that about how you created this list.(Skip the part mentioned above)
    2. Please also share with me a template about your related list.

    To protect your privacy, please send us your related info via Private Message.

    Please have a try and share with me your result.

    Thanks,

    Neo

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-09T13:46:33+00:00

    Hi Qing,

    Thanks for the prompt reply. What I'm seeing is slightly different to your screenshot, but still similar.

    When going to Settings > Library Settings and then selecting the column, I see:

    It is using a closed term set, and so Fill-in choices have been automatically disabled. There is no default value. Under List Content Type, it is possible to see that the column is set to optional:

    We did indeed test the same document library (our site only has one document library) with the new and classic experience. The issue only occurs in the new experience. As shown in the screenshot below, when uploading a document to the library, it is not marked as a required field and I am allowed to leave it blank.

    However, after selecting a value in the 'Client' field and saving it, I receive the error message shown in the screenshot of my original post stating "You must specify a value for this required field."

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-09T11:13:48+00:00

    Hi Brent,

    Based on your description, I suggest you confirm if you have checked Yes under the option “Require that this column contains information” on the list or library which is using New experience:

    1. Sign into the list or library which is using new experience.
    2. Click Settings>select List Setting.
    3. Click the column under Columns
    4. Check if check Yes under the option “Require that this column contains information”, if so, please select No.

    If the issue still exists, could you please provide the following information?

    1.  The screenshot of the affected column’s settings.

    1. Confirm if you use the same list or library with the new experience and classic experience.
    2. Check if all lists and libraries have the situation.
    3. Confirm if you reproduce the issue via the following steps:

    a. Add a new item, select a value on the managed metadata column.

    b. Edit the item>remove the value>can’t save.

    1. The steps about how to create the affected column.

    Thanks,

    Qing

    Was this answer helpful?

    0 comments No comments