Forum Discussion
HelenaStarenby
Apr 15, 2020Brass Contributor
Menu not updating
Hi, what is wrong with the menus in SharePoint? The changes only show on the computer I am using for editing the menu. This is the case for both "website menus" as well as hub site menus. It has been...
JaH
Nov 13, 2023Brass Contributor
This is a shining case of Microsoft SPO dev and service teams racing to the bottom.
The Structured navigation provider (there are at least three if you count the broken client-side provider) is heavy on the SQL transactions which translates into $$ (which isn't an issue if you've costed for it on your own infra, but hey race to bottom). So instead of updating their providers to use caching and update flags like any sane team, they are completely throwing the baby out with the bathwater creating a broken customer experience. The reason? because Greenfields and Agile can be easily used as a crutch to justify the impact. Putting the impact behind third world support is the polish on the s**t.
In this case the reason it's not updating is because (speculating based on MS Support stating you need to wait 24hrs) they are putting it behind a timed update job that runs very infrequently (12 hrs or so). So you have to wait for that job to run instead of it simply being a simple update flag for clients to update.
It's really, poor business practices at the end of the day, SPO teams have a poor understanding of the implementations on enterprise applications, and the company of accountants should know this by now especially if they want to attract more enterprises. 365 is just not reliable enough for LOB processes because Greenfields, because Agile...but really, because "race to the bottom".