ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Importing object without "Keep existing folder links" is not working


Article ID: 140634


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine


Importing objects while not ticking the option "Keep existing folder links", behaves as if the box was ticked.

This means that if the object already exist in a different folder, the new object is not created in the current directory but a link is created. 

This is true for AWI, Java GUI and the keepFolderLinks boolean of the ImportObject API class.

So, assuming the object already exists in the target system, and is being replaced, the option "Keep existing folder link" should work like this:

true: Any existing folder links for the object are left as-is. If the object is imported into a different folder than its current home folder location, a link is created in the target import folder.

false: Regardless of the object’s current home folder, the object’s new home folder is the target import folder. All other links are deleted.

Now, regardless the "Keep existing folder link" option, it behaves as if the option were set to true.


Release : 12.0 / 12.1 / 12.2 / 12.3



This issue has been corrected for the import of individual objects or several objects.

NOTE: The issue is NOT yet correct in the case of an import of a folder containing objects.


Update to a fix version listed below or a newer version if available.

Fix version:

Component(s):Automation Engine

Automation.Engine 12.2.5 - Available

Automation.Engine 12.3.2 - Available

Automation.Engine 12.1.8 - Available

Automation.Engine 12.3.2 HF2 - Available