Still the need for Classic Explorer
The article discusses the need for the Classic Solution Editor in Microsoft Dynamics 365. The author encountered an issue while trying to change the width of a field in an unmanaged environment and received a generic SQL Exception error message. They tried to download log files, but it was not possible. The author then tried the same operation in the Classic Interface and received a SQL Server error message, but was able to download the log file. The log file revealed that the column the author was trying to modify was dependent on another column and was used in a calculated column. The author concludes that until Microsoft resolves this issue, there is still a need to use the Classic Solution Editor to understand why certain operations are not working as expected.
Article 22m
Login now to access my digest by 365.Training
Learn how my digest works
Features
- Articles, blogs, podcasts, training, and videos
- Quick read TL;DRs for each item
- Advanced filtering to prioritize what you care about
- Quick views to isolate what you are looking for right now
- Save your favorite items
- Share your favorites
- Snooze items you want to revisit when you have more time