Deploying a customization that overtakes a base method (rather than overriding it) fails as a hard error for one developer but only shows as a warning for a colleague on the same Cloud environment and the same Developer Studio version. Why the inconsistency, and which behavior is actually correct?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

'Base method should be overridden and not overtaken' is a P2 Static Code Analysis (SCA) error, and it should be treated as an error, not a warning — the colleague seeing it as only a warning almost certainly has SCA checking disabled via the 'NoErrorOnStaticCodeViolation' feature toggle under Project Properties > General > Feature Toggles in their Developer Studio instance. That toggle should be left unchecked so SCA runs and enforces this as a real error; disabling it just suppresses a check that's there specifically to catch this kind of unsupported overtake before it causes runtime/deployment problems.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions