Skip to main content
Question

Developer Studio Static Code Analysis issue

  • September 11, 2026
  • 1 reply
  • 32 views

Forum|alt.badge.img+6

Hi IFS Community,

 

I’m not able to deploy my customized DataCaptRegstrArrivals-Cust.plsql file anymore due to a priority 1 Static Code Analysis error that appears in Developer Studio and was not there some weeks ago:

 

Followed following advice from DataCaptProcessTemplate.plsql but it didn’t work because Developer Studio seems to accept “@DynamicComponentDependency” for private procedures only:

 

Tried to surround the parameters with $IF Component_Wadaco_SYS.INSTALLED $THEN … $END

but Developer Studio does not accept it.

 

Also tried to surround the whole procedure  with $IF Component_Wadaco_SYS.INSTALLED $THEN … $END.

Developer Studio accepts it and generates the code, but the full procedure body is copied in DataCaptRegstrArrivals.api which leads to an error in the package declaration after deployment. 

 

Does anyone has an idea for solving this?

Thanks

1 reply

  • Do Gooder (Employee)
  • September 11, 2026

Hi ​@ChristianJ 

Parameters cannot be wrapped with conditional compilation, and public, private, and default methods are not allowed to use the @DynamicComponentDependency annotation, as this could lead to deployment errors and significantly increase build time.

The underlying implementation of @DynamicComponentDependency uses conditional compilation ($IF conditions). Therefore, the entire procedure/function cannot be wrapped with conditional compilation. However, conditional compilation can be used within the body of the procedure/function.

This is not a bug in the SCA tool, and this is the expected behavior. Therefore, this needs to find an alternative approach to pass the parameter to this method.