I'd get rid of the bracket using a regex replace then do the padding, can be done in one statement
@PadLeft(@ReplaceRegEx(@Value(Lat seconds),\x{0029},""),5,0)
Wouldn't it just be @Left(@PadLeft(@Value(LatSeconds),2,6, 0),5)
Though I would probably use @PadLeft(@Trim(@Value(Lat Seconds),")"),5,0) instead.
Thanks gents, both work great! I'm still working out how to combine string functions. The help pages are not very user friendly on this topic. Do you know if this is documented better anywhere?
Thanks gents, both work great! I'm still working out how to combine string functions. The help pages are not very user friendly on this topic. Do you know if this is documented better anywhere?
They're just nested functions, the entire first function in bold, becomes the string value of the second function
@PadLeft(@ReplaceRegEx(@Value(Lat seconds),\\x{0029},""),5,0)
Personally, if your data is as per the screenshot, I'd use a single stringreplacer to get rid of the brackets across multiple attributes at once, rather than trying to do it individually with multiple string functions in an AttributeManager
p.s. neither of us are gents :-)
Oops apologies!
This is what I'm trying to achieve - thanks for the tip! How would I do that from the one stringreplacer transformer?
Oops apologies!
This is what I'm trying to achieve - thanks for the tip! How would I do that from the one stringreplacer transformer?
You can select multiple attributes in the string replacer, then choose to replace the bracket with nothing

You'd still need an attribute manager/string padder for the next step so if your absolute goal is less transformers then it might not be the solution you want. Makes for a much more readable workspace though and quicker than trying to get nested functions correct
You can select multiple attributes in the string replacer, then choose to replace the bracket with nothing

You'd still need an attribute manager/string padder for the next step so if your absolute goal is less transformers then it might not be the solution you want. Makes for a much more readable workspace though and quicker than trying to get nested functions correct
I agree, much clearer workspace, otherwise I have to remember what was done in the attmanager. Your a star! :)