1
We have an issue with a field name in a table. The field was marked as obsolete and recreated with error corrections since field names can't be changed without making destructive changes.
The code analysis still throws a warning and even an error in future runtimes although it is marked as ObsoleteState=Removed.
My suggestion is to exclude obsolete fields from code analysis.
STATUS DETAILS
Needs Votes
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team