We're testing D365 v9 (both online and on-premise, at the moment). We noticed that an OOTB status reason we'd deleted from Opportunities was for some reason back after importing our v8 solution into v9. We deleted it again - which it happily let us do - and it broke things. Specifically, we couldn't edit the field any more, or go to any Opportunity fields. This status reason is not used anywhere, and the status reason field displays on a view just fine.
The error text that shows either when editing the field or when going to the form is "An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code". The logs just have a "System.NullReferenceException: Object reference not set to an instance of an object" exception. I could understand if this error was just happening on the form - I can't find any reference to it, but there might be something I'm missing. But why would the field edit be broken as well?
Anyway, we've got the system back to normal, by exporting that field from a new org and importing into the broken systems. But just wanted to highlight this for others. Will report it as a bug as well.
*This post is locked for comments
