I had a lot of columns set up in a dataview.
They are now all gone. I can’t set up any new ones either, in that dataview or a new one.
WTF.
I did start a new app, and try it, and it saved. So something is screwed in my app.
Anyone come accross this?
This in production or pilot?
I’ve had layers get corrupted plenty of times but haven’t seen this DV columns not saving version of it.
I’m looking in the json, they are there.
The eventually vanished.
Not on my screen though.
pilot
I’ve had layers get corrupted, hidden columns remain visible, column order randomly get out of wack, etc. Only consistent fix I’ve found is deleting the DV or component and starting over 
I got the team here wondering if we can stick with Kinetic given the extensive customizations they want to invest in and whether the stability of the platform will stand up to how critical the customization is and whether we can afford the constant maintenance that comes with the cloud upgrade cadence. Trying to write up an email laying out the facts. I can’t link every thread here, but it’d be negligent of me not to bring up these things.
I’m having the same issue in Live.
I’ve had similar issues in our system, live, pilot, and 3rd. Talking with support, they believe that the layer is corrupted in certain segments. Meaning that the overall layer still “functions as intended” but certain things just won’t show correctly, much like @Randy described.
My workaround has been save often and export the layers just as often. Even then I still have some dataviews with custom columns written up similar to yours where none of them show. The only thing I have been able to do is keep track of what I added column-wise and when I added it, + hope that I wrote something to them so they show accurately in the debugger menu. If not I just have to make a new column and keep going. Alot of these layers are too far into their development cycle for me to restart / destroy the dv and build a new one without troubleshooting/rewriting/repointing a bunch of events.
Sorry if none of this is helpful, but wanted to share in the misery XD
Yeah, new ones added don’t work or stay either…
Also a new DV doesn’t keep it’s columns 
So you can’t see them within the dataview, but can you still write to them and “see” them in the debug menu like with the ctrl+alt+v inside your dataview? If not can you row update their value forcefully and see if they show in the dv then? I had success just forcing them to write even though they didnt show.
Also what browser are you deving in? How often are you closing out of your browser and going back into it?
No, they eventually disappear altogether like they were never there.
Brother, that sucks!
I’ve never had them fully give up the ghost… like usually there are at least bits and pieces you can scratch at to keep them working.
Has support said anything on the matter?
I gotta figure out how to reproduce it first.
A new one worked. Not a clue how it stops.
I’m sorry man.
It sounds maybe like XXXDef dataviews.jsonc got corrupted for that app on disk, maybe pull the json out of xxxdef.content and look for syntax errors? (not from MetaFx.GetApp because that passes through the translation layers in the BOs)
I have caused similar problems to myself by directly editing the json in xxxdef.content and introducing syntax errors since i wasn’t passing through a syntax validator. it would load but changes etc. would fail to save since the BO couldn’t parse it anymore.
I would be completely unsurprised if AppStudio managed to do that itself.
Gabe to the rescue!
Well, who knows, Epicor could be doing any number of other things too. That’s the fun part of it!