Left function issues when importing/exporting releases

[AdamSørensen]

Hello, We upgraded to Version 5 not long ago, and have experienced some issues with the Left function. When I export a release with the left function syntax Left(var1, 10) in Objects/Processes, it automatically transforms to Left(var1; 10) when importing said release. This then Returns an Internal Exception when runned. Anyone have any idea what is causing this? It's pretty annoying changing the syntax everytime we import a new release. -Adam

[John__Carter]

Hi Adam, I've not heard of anything like that. If you open the exported file and look inside the XML, has the comma been replace with a semi-colon? If not then it would suggest the import logic is making the change. So after importing, if you export again and look at the XML, what do you see? And after correcting the error, if you export and then import again, what happens?I think it might be worth raising this with our Support team - please provide them with example before and after XML, and details of your BP version/OS version/language and locale settings etc.

[AdamSørensen]

The default Left, Mid and Right functions is returned with the syntax Left({Text}; {Length}), i.e. with semicolon seperating the arguments. In fact, every operation with two or more arguments are seperated with the semicolon instead of a comma. Very strange... When I export the expression: Left(""abs"", 1) in a calculation stage The exportfile shows:

[John__Carter]

Hmm yes, strange. So exporting to XML you would expect to see Left("abs", 1), and if even after re-importing then exporting again the XML stays the same, then that suggests it's not the export/import logic that is introducing the error. Maybe it's Process Studio interpreting the XML - but that does sound weird. If you copy the calculation stage into Notepad, do you see the same XML that you would if you exported, or has it been corrupted?It doesn't feel like we'll find a resolution using this forum. It might be best to raise a support ticket.