I think there were like 3 items it recommended for the use case (also Bo, I originally asked it to help me with regex for 33 vendors and it led me back to recommending Lookup values in multiple rows. I tried to be lazy and get sculptor to do it for me lol 33 is a lot and I found out that there'll be a total of 40-60 vendors overall):
- 1.
Lookup values in multiple rows -- (can't loop through comma separated values)
- 2.
Claygent -- pointing clay to another table (can't do that -- unless I'm mistaken?)
- 3.
HTTP (which I didn't try because I didn't want to go in a rabbit hole)
But out of the first 2, these are items that are capabilities that don't work in Clay, so why would it recommend it? That's why I think perhaps Sculptor still needs training on the product capability?