To be honest, as there was a slight difference with the non-working and the working Substring, here it goes the corrected one, now exactly 100% as the original one (because I wouldn’t be surprised that some of the “collaborationist” users in the forum would use that irrelevant detail to attack me):
Hi @pere
About this one post:
If this happens in the future, could you reply in this topic with the content of a copy paste of the activity before “fixing” and after? What I mean by that → when you copy an activity in Studio, you can paste it as raw text anywhere else, like a notepad or the Forum post.
This will hopefully showcase the difference in the underlying xaml of the activity and put us on the right track to figuring out why this is happening. It looks frustrating.
As to the fixes and improvements I can think already, I feel like we should issue validation errors individually per each line of the multiple assign, and not just a blanket one as it is now.