Good morning,

I am using the TrimStart function (VC7.17) to strip off the root portion of a file path resulting from a List Folders task in order to recreate the subsequent directory hierarchy elsewhere. This is done using a loop on the create folder task.

\\KANSN005\Common_Data\Transfer\Production\Merx\MAXOutput\{STRING(TrimStart|{LOOP(CurrentValueX)}|{TRIGGER(a99ac2dc-6c45-4aca-94c7-fc0042781479|LastTrigger|File.Folder)})}

When applied the source folder is as follows:

\\kansn005\Common_Data\Transfer\Production\Merx\ZIP_IN\PR107845.A001.U\OtherFolders

The result of the TrimStart is 'R107845.A001.U\OtherFolders' where the leading character 'P' is missing.

Entering the raw values into the test area in the variables window presents the same issue. It appears the trim is a little over zealous in its removal of the leading string.

{STRING(TrimStart|\\kansn005\Common_Data\Transfer\Production\Merx\ZIP_IN\PR107845.A001.U|\\kansn005\Common_Data\Transfer\Production\Merx\ZIP_IN)}

Result: R107845.A001.U

I am not 100% sure what causes this if it is something about the backslashes. We do not process the actual data ourself much, just pass this on to the TrimStart function in .NET. I did some tests but could not really find what was causing this.

---

We found it now and will publish a build next week. Thanks for the report.

---