reedpamsft
reedpamsft
@SPJS @juliemturner I've made a configuration change that should take effect in the next 15-30 minutes which should put you back in the state of loading "classic modern" (as Alexander...
@juliemturner thanks for confirming!
@heinrich-ulbricht "new modern" currently supports App-level SPFX customizers, and we are working on supporting command set customizers right now (a bug in that work is what caused this recent issue).
@shaipetel does this happen when you go to the view, or when you try to save a value?
@shaipetel anyway, you can hide columns by going into the list settings, then going to any views with the issue, and unchecking lookup columns so they don't show up. The...
Thanks @shaipetel . I'll look into the back-end details for your list and see what might be causing this. Regarding release timelines, we have two procedures by which we release...
As mentioned, I'm pushing for a reevaluation of the process I mentioned. I also don't and can't speak for Support and what they may have said on past cases.
@shaipetel just as a note, your default view (allitems.aspx) does indeed contain 13 lookup columns in it, which is why you're getting the error. Most of the time when a...
Thanks for the mention! I wasn't aware of this... How are you updating the items? Directly calling APIs? Using a particular js library?
Sorry, it's on our radar now as a thing to fix. I'm actually surprised this doesn't work, so the investigation into how to fix it might be a little complex.