Convert & Update Node Suggestion

[JefferyD]

Most of the times when I'm converting dates, I'm doing so for multiple dates across an array of nodes. If I try to apply a ForEachNode for the service, then the resulting conversions cannot reliably be merged back as there's no key to merge back with.

Given the below setup, there's no easy way to reliably match a converted date to the original date that it was converted from.

ToDate Example.PNG (53.63 KiB) Viewed 992 times

ToDate Example.PNG (53.63 KiB) Viewed 992 times

ToDate Example Result.PNG (49.74 KiB) Viewed 992 times

ToDate Example Result.PNG (49.74 KiB) Viewed 992 times

This can alternatively be handled using a loop method, but that is a lot of setup to just convert dates and it can also produce a lot of logs making debugging a bit more complicated than seems necessary, especially for particularly large arrays.

I've mostly encountered this with the ToDate service, but this can also apply to many other conversion services.

Data Conversion Services.png (23.46 KiB) Viewed 992 times

Data Conversion Services.png (23.46 KiB) Viewed 992 times

Suggestion
For scenarios where bulk conversions are necessary, it would be nice if a node path could be used in place of a value that would convert it into and append a new node to that path just like how InsertAndUpdateNode functions.

InsertAndUpdateNode Service.png (84.59 KiB) Viewed 992 times

InsertAndUpdateNode Service.png (84.59 KiB) Viewed 992 times

InsertAndUpdateNode Result.png (70.26 KiB) Viewed 992 times

InsertAndUpdateNode Result.png (70.26 KiB) Viewed 992 times

[CathyC]

There is a more recent forum post where we were discussing this
viewtopic.php?t=678

[JustinVanRegenmorter]

Task 11394 has been created to discuss this feature.