I’m not exactly sure how this new feature works. I tried achieving what I used to achieve with the data transformation community node and I was unable to reproduce the same results with the autocomplete feature.
That’s helpful to know. Would love to better understand - could you maybe share some screenshots of what you tried to do? Or what was confusing about the autocomplete?
Anything you could share there would be very helpful. It’s a relatively new feature, so I want to make sure we get a handle on any UX issues ASAP. Cheers!
Hey all. Just wanted to stop by and ask if anyone has used our AI Transform node already? It should theoretically be able to solve all the text replace use cases.
Excited to hear your experience with it!
Cannot find the node on 1.56.2, was it recently added? Do not see it in the release notes.
Also. this is using AI I assume with that name, so all simple text transformations are done by AI?
Personally, I feel that is a bit excessive to use AI for that. Of course AI can be very useful for more complicated transformations, but using it for all the simple stuff sounds like a bad idea.
@BramKn I think it’s only available on Cloud at the moment (since 1.55). It creates matching code via AI for you once, so it will only use AI once and then use the created code.
1 Like
Ah ok, that makes sense, thanks. 
Thanks for sharing!!
1 Like
Given the alternate possibility of using an expression, code node or edit fields node, a possible solution would be to allow users to save reusable functions to extend the built-in ones. For instance, I need a “slugify” function very often to craft filenames. It might be worth being part of the core lists of functions or not, but either way I’d be eager to implement it as a reusable function that no-code users or myself can then reuse in code nodes and expressions. Would it be tricky to add? I don’t see any security risk (since you could already write similar functions in expressions even without a code node), auto-completion might be more complicated though.