Posted Tue, 23 Apr 2019 17:41:31 GMT by

 ... in our case this was caused by custom descriptions we added to individual steps. Not sure which ones actually caused the problem, but after deleting all step descriptions and custom step descriptions, I was successfully able to import v9 .aml files into v11. (v11.1.20.19 to be precise)

Just FYI in case someone is interested.


Posted Wed, 24 Apr 2019 02:05:55 GMT by

Hello Daniel,

Thank you for the data provided. Was there a case created for this issue? If not, we will create one to document and submit as a possible bug.


Posted Thu, 09 May 2019 06:53:57 GMT by

Is this resolved or planned to be fixed in upcoming release? 

Posted Fri, 10 May 2019 01:43:26 GMT by

Thanks for this info. I will remove the descriptions and run my own tests.

FYI - I have a test that only had a msgbox that says "Test" and that did will not import.

Posted Wed, 18 Sep 2019 02:11:09 GMT by

HelpSystems, is this issue resolved in current available release?  We have hundreds of tasks and 1000s of steps that would need this resolved on.

Posted Thu, 19 Sep 2019 23:56:19 GMT by

Hello Nick,

Unfortunately it looks like Daniel didn't get a chance to provide a case or bug number, so I cant confirm that specifically.

However I did a quick test internally and did not experience any error when importing a v9 task which has a custom step description into v11.

You must be signed in to post in this forum.