has anybody experienced this?
I suppose some day I could be thankful this is documented, but imagine spending resources on orphan reconciliation UX instead of fixing why AppStudio borks my layers on the daily while simply not introducing breaking changes to Base.
It was a huge problem in 2022 and 2023, I still have layers that were built in 2023.1 that flash an orphan components error on load (but then it disappears). Basically would have to rebuild it to fix it since the are no orphan components visible in app studio to do anything with.
Just toss us a json editor, move this from AppStudio ‘Fundamentals’ documentation to a kb article and get back to general stability work until you can later solve how to handle this gracefully in the mysterious layer merge.
I mean, we can already edit the json. The issue is there is no ide to preview the changes and the upload process is ridiculous since everything has to be zipped up.
Right I mean drop a code view into AppStudio. Done.
Remember coldfusion? Something like that would be amazing where if you want to do wysiwyg you can, and if you prefer to just write the code, you can. Everyone is happy.
Don’t want to remember but yeah. It’s pretty standard it least far an escape hatch. Like edit json, preview and 3-deep ‘undo’ is all we need.
And people will say they can’t do it because they need to stop us editing base code. But this was solved in classic - in the script editor you could view but not edit the base code, and then you could still write your own code. So I just don’t buy that there is some technical limitation here.
Yes nearly every major upgrade creates orphaned fields in our customizations
The thing too is it’s not even code. It’s Application Definition schema. Sure we could mess it up in a code editor but it either validates to the schema def or doesn’t.
Ironically, many of the AppStudio errors on save which are silent and require you to crash out and lose work are related to the wysywig designer. Like remove a task mid event and join in a new one. Crash - connectors collection messed up. drawing a line between pretty images is broken.
Just give us the json so we can fix up the dang task order while you work on your broken pretty diagram.
Or at least raise the error and revert the change to valid state rather than suppress the error and crash. (3-deep undo)
YES this drives me absolutely up the wall. It just stops responding. No error message, no clue what is wrong, no opportunity to recover your work. Completely unacceptable.
3-deep undo. Done
You mean you’re not running browser devtools on AppStudio? we’re the testers you know. 
It usually doesn’t show me anything?
There’s a checkbox to break on trapped errors. It’s a mess. Don’t recommend but may add details when desperate for those forever support cases.
Where?
This please, seems like a easy path to take
I don’t know this to be true and they’re for sure smarter than me but I fear the problem may be its designer-first rather than code-first. Meaning it only works IF wysiwyg.
Unfortunately what-you-see-is-not-what-you-get so crash.
If true then handling connector errors for example in designer is needed even tho it’s just an ordered actions array n there’s no such thing as a connector in the json.
If it were code-first then handling, reverting json and rerendering the pretty icons is more straightforward. 
I know for a fact this is not the case.
