IFS Developer Studio - bugs

Hi ​@CgiTomasG ,

Hi ​@hamalk 

New IFS Developer studio have a serious bug: it's impossible to depoy cdb, ins, or rdf files if they contain more than one section. Deploy always executes the first section or hangs, so you have to upload the file in parts.

Can someone fix this quick?

 

 

for example I got no exception and only output to failed line when executed from opened file. But from tree view ( via rmb) it failed with message.

Looking into this, will try to deliver a fix asap.

/Andreas

hi ​@InfFilipV 

We will fix the  CDB script files deployment issue soon. Already created a defect in Jira and fix is in progress. Thanks for reporting it. 

/Harshini

Hi ​@InfFilipV 

We will fix the bug and it will be available in the next tool release we do in Developer portal. Internal Jira has been created and the fix is InProgress. 

/Harshini

​@hamalk thank you :)

Hi hamalk,
another Error fro “Generate DDL Source” , both module and Entity

Hi ​@InfFilipV 

Error for “Generate DDL Source” has been fixed in 26R1-EA release, we will down port the fix to 25R2 track with the next tool release which we are planning to do with 25r2-GA release by end of May,

/Harshini

Hi,
thanks for info - any workaround till that?

Should we manually copy CDB and left only changes up to Core?

BTW, was this all EBR / Online Execution tested in Customization projects?
We are still confused on correct approach fo Online execution support. (eg. difference between ddl and ddlsource, correct content of ddlsource, ...)

Hi ​@InfFilipV 

Until this is fixed in the tool, you need to handle that process manually.

Yes we have tested the online upgrade for customizations. ddlsource were not tested as these files were introduced with NZD online upgrade features in 25R2 itself  and not previously exists with customizations. 

Hi,
got this issue in projection action. I thought that at least one version should work. Or at least error could be better.
 

Hi,
I have another problems. ​@hamalk 

1. Dependency Not Found is now Error,

even if it is inside Cust project, where all modifications depends on exact solution set configuration and once is module purchased, it cannot be removed, we are forced to use conditionalcompilation.

anyway, it does not work.
I have here static dependency between CMOD and ENTERP and it fails to generate and deploy.

Now it block me to deploy years old code and probably requires total refactor of foreign old code.

2. DependencyHints - all of these objects are inside same CMOD module i guess it is just another error which is present only in Cust layer, since IFS does not care about testing it.

What I should refresh to make it works?

Validating CCnPmtUtil-Cust.plsql
-----------------------------------------------------------------
CCnPmtUtil-Cust.plsql has 2 error(s), 13 warning(s) and 0 info(s)
-----------------------------------------------------------------

 ¤ [Priority 1] DependencyNotFound
	 {Line 567} No dependency found for COMPANY_API, owned by module ENTERP.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 731} No dependency found for COMPANY_API, owned by module ENTERP.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.

 ¤ [Priority 4] DependencyHints
	 {Line 313} C_CN_PMT_CONFIG_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 318} C_CN_PMT_CONFIG_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 332} C_CN_PMT_CONFIG_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 335} C_CN_PMT_CONFIG_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 363} C_CN_PMT_CONFIG_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 483} C_CN_PMT_CONFIG_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 604} C_CN_PMT_AP_ITEM_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 625} C_CN_PMT_CONFIG_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 722} C_CN_PMT_AP_MATCH is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 733} C_CN_PMT_CONFIG_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 779} C_CN_PMT_AP_MATCH_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.
	 {Line 799} C_CN_PMT_AP_MATCH_API is not connected to any module. Dependency could not be derived.. . If the dependency is dynamic, then conditional compilation needs to be used.. If you have already added the dependency to deploy.ini but it has not been included in a build yet, you can manually add the dependencies in your development database using Installation_SYS.Register_Dependency. . Do not include this call in any scripts though as in deliveries this has to be controlled by deploy.ini.

Hi ​@InfFilipV 

 Dynamic dependency behavior has changed with the 26R2-EA tool release, which is why you're seeing this now. This update was requested through a swarming ticket,  (https://ifsdev.atlassian.net/browse/SWARM-6894). We made the change in https://ifsdev.atlassian.net/browse/DXDEV-5755.

This adjustment helps restricting code generation at the tool level rather than resolve deployment issues during build time . Developers now need to proactively address these issues during development.

The error itself is self descriptive and developers can follow the tips given in the tool tips and do the fixes 

register the dependencies in the database using Installation_SYS.Register_Dependency and perform a “Clear and Refresh Code Completion Cache” using the RMB menu

Hi ​@InfFilipV 

 

 Dynamic dependency behavior has changed with the 26R2-EA tool release, which is why you're seeing this now. This update was requested through a swarming ticket,  (https://ifsdev.atlassian.net/browse/SWARM-6894). We made the change in https://ifsdev.atlassian.net/browse/DXDEV-5755.

 

This adjustment helps restricting code generation at the tool level rather than resolve deployment issues during build time . Developers now need to proactively address these issues during development.

 

The error itself is self descriptive and developers can follow the tips given in the tool tips and do the fixes 

 

register the dependencies in the database using Installation_SYS.Register_Dependency and perform a “Clear and Refresh Code Completion Cache” using the RMB menu

• My project is 25r1, why is affected by change for 26r2 ea?
• refresh is not mentioned in “self descriptive “ message
• it did not help, even after DS restart and all available caches refreshed
• 2. Warning is about objects in same module that’s also ok?
• Links to JIRA are useless for non ifs users, do you have any CSM KB or Community description? All changes in DS are done out of blue and without proper info to external users

Hi ​@InfFilipV 

 

 Dynamic dependency behavior has changed with the 26R2-EA tool release, which is why you're seeing this now. This update was requested through a swarming ticket,  (https://ifsdev.atlassian.net/browse/SWARM-6894). We made the change in https://ifsdev.atlassian.net/browse/DXDEV-5755.

 

This adjustment helps restricting code generation at the tool level rather than resolve deployment issues during build time . Developers now need to proactively address these issues during development.

 

The error itself is self descriptive and developers can follow the tips given in the tool tips and do the fixes 

 

register the dependencies in the database using Installation_SYS.Register_Dependency and perform a “Clear and Refresh Code Completion Cache” using the RMB menu

 

• My project is 25r1, why is affected by change for 26r2 ea?
• refresh is not mentioned in “self descriptive “ message
• it did not help, even after DS restart and all available caches refreshed
• 2. Warning is about objects in same module that’s also ok?
• Links to JIRA are useless for non ifs users, do you have any CSM KB or Community description? All changes in DS are done out of blue and without proper info to external users

At the very least, could you not include an option to make dynamic dependency a warning instead of an error? If that is not possible, can you provide a link to a version of IFS Developer Studio that isn’t going to set us back weeks? It’s not like our customer focused solutions are suddenly going to not include the cmod component and not execute at all.

Hi ​@InfFilipV 

We made this change in behavior following several customer requests to prevent deployment errors caused by improper handling of dynamic dependencies in the code.

These errors existed before and showed in the tool editor but were not enforced as strict quality gates during development. With the latest tool release, 26R1-GA, we have now made these errors hard stops, preventing code generation until developers resolve them.

This update applies to all previously supported tracks, so you may encounter new errors that were previously missed due to this stricter quality gate.

I will create a KBA for this feature and share with you.

If you follow the error instructions and clear and refresh the cache, you should be able to resolve the errors after adding the necessary conditional compilation statements in the affected code.

/Harshini

Hi ​@hamalk,

• basicaly, I’m OK with this “improvement” but
  • It cannot be forced by “random” release of DS, this is so big change, that it will take lot of time, which noone will pay
  • Such change has to be introduced with some SU or RU and communicated ahead
  • this cannot affect all RUs backwards
  • it was warning for decade(s), it should be optional per project
• did you really though about Customization layer development?
  • Customizations are so tightly connected with particular solution set, that using conditional compilation is just not necessary overhead.
• Please finally show deploy.ini files in “Projects” navigator or introduce RMB same as for modifing SolutionSet
• seems like, here was originaly used Dynamic and then changed to STATIC - but execution of “Installation_SYS.Register_Dependency”  do nothing then...

  • 

  • 

     

    

     

  •  

    

  • 

​@HoustonHockyMon 

in case of “emergency” need, there is option to skip this errors, but it is not safe to have this enabled for longer period…
 

Hi ​@hamalk 

Please supply the KBA number - I am also seeing many of these dependency errors now on customisation files and we are also on 25R1, so I completely concur with the comments made by ​@InfFilipV and ​@HoustonHockyMon 

It’s tempting to use the NoErrorOnStaticCodeViolation option but obviously not good!

Thanks

mmck