Required choice column reverts to previous choice in library

[kmktnn]

In a library, if I work with choice columns (not required), all is normal when I edit the file.

However, if a choice column is required, when I update the document, the choice in the columns reverts to the previous selection.

Do you experience the same behaviour? Did you find an explanation?

[#2]

After more testing, this incorrect behaviour happens when the document is opened in the application and not in the browser, additionnaly to the required choice column. Same behaviour in 'private browser'.

[#3]

After more testing, we understood the conditions when it happens:
- only Excel files, only when the file is opened in the client application
- all types of columns: choice, text,...
- all browsers, even in private mode
- all sites and libraries
- all users

Steps to achieve the wrong behaviour:
- in a library, change a property of an Excel file
- open the file in the application
- go to File > Information > Show all properties
- the property is not updated in the file

We opened a ticket with Microsoft. Their first recommendation was to synchronize the library. We also realized that the property would update if we waited more than 1 min and refreshed the page before opening the Excel file.

And finally, we found that it was a cache application problem.

To correct the behaviour, in Excel, Open File > Options > Save:

• Click on ‘Delete cached files’
• Check ‘Delete files from the office document cache when they are closed’

[#4]

@kmktnn The root cause you've identified, which is related to the way Excel handles the caching of document properties, is an insightful finding. It's often these seemingly innocuous client-side factors that can have a significant impact on the user experience, and your persistence in uncovering the underlying issue is commendable.

The recommendation to clear the cached files in the Excel options is a pragmatic solution that should address the problem for end-users. However, I would encourage you to explore potential long-term strategies to mitigate this issue, such as educating users on the importance of regularly clearing their cached files or investigating any Excel or SharePoint configuration settings that could help prevent the caching behavior from causing problems.

Additionally, it might be worth considering whether there are any SharePoint-specific solutions, such as custom scripts or web parts, that could help streamline the update process for these required choice columns and ensure a more seamless user experience. While the client-side caching issue is the primary driver of the problem, there may be opportunities to enhance the overall functionality and reliability of the solution. I'm grateful for your diligence in troubleshooting and documenting this issue, as it not only helps resolve the immediate problem for your organization but also contributes valuable insights that can benefit the broader SharePoint community.

Please feel free to reach out if you have any other questions or if there's any way I can assist you in further refining your SharePoint environment and addressing similar challenges that may arise in the future.