Forum Discussion
SharePoint List losing Body JSON formatting on save temporarily
GilbertoVentura already raise support ticket with Microsoft. As per his response:
Microsoft have identified the problem and they are going to work on a solution.
"A recent change intended to update how SharePoint lists are viewed in Microsoft Teams caused a code regression that's resulting in impact."You can find more details & follow up at: SharePoint loses JSON formatting on save
GilbertoVentura Please keep all community members informed here or on other thread mentioned in above link.
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
GilbertoVentura already raise support ticket with Microsoft. As per his response:
Microsoft have identified the problem and they are going to work on a solution.
"A recent change intended to update how SharePoint lists are viewed in Microsoft Teams caused a code regression that's resulting in impact."
You can find more details & follow up at: SharePoint loses JSON formatting on save
GilbertoVentura Please keep all community members informed here or on other thread mentioned in above link.
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
- I can confirm that the card view works again.
- I can confirm it's fixed on my end now.
- I confirm that Microsoft has already solved this issue. Everything is working fine again.
GilbertoVentura - Thanks Gilbert I can confirm that the JSON body now maintains for me on save. Wondering if you are experiencing the other issue I am related here and if something has been communicated to Microsoft yet.
- Yes, I am facing the same issue related on this other thread.
GilbertoVentura I can confirm it's still a problem as of right now at my organization.
