This also works and seems a little easier to understand. Instead of searching for the indexes of the open and close parenthesis and using a substring, it just removes everything that isn’t a numeric value. Great solution provided by nsingam, but in the spirit of offering you options, I thought I would share this one with you too. Definitely there are more than 1 way to skin a cat (horrible expression).
$[‘betroffene IT Systeme’].map(x => x.replace(/[^0-9]/g, ‘’))
Thank you for your answer, much appreciated. That I haven’t tought about that also. Because I always only need the numbers.
Regards
Jens
thanks a lot Shayne, I will go with parameters and try using the underscore syntax to pass them out and along the workflow. will post again later with an update on how i got on 🙂
hmm, snaps vs scripts table could be a bit more prominent in the help/docs… ie Script snap:
Does not support pipeline _parameters
Supports only Document input/output
Does not support Accounts
Often awkward to debug
Cannot be unit tested
I agree the Script snap is awkward to debug… :). And am surprised there’s no feature to pass in/out parameters. Some stuff cant be achieved with the standard Transform snaps, but i have to fake a document as a ScriptHook input to pass in a parameter and then try and work out the syntax with the Mapper to take the subsequent output and write that to a pipeline parameter to be used later in the flow by other snaps. I thought it would be simple/quick to do some basic js/python in a Script but looks like i may have to author a custom Snap with the SDK. Will persevere a few more hours with the Script snap…
