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
New