Hi @NCorver the search module is a "user friendly" module - and no you couldn't search by that. You'll need to use the customAPI module. In the module you'd add query arguments to match you search.   Note if you need to you could add another level  {parent}.{parent}.{parent}.{parentID}  

Hi @NCorver Thank you for sharing! So I see two ways:  in your search, if you use the custom API module, you can say e.g. parent:parent:name = XYZ OR:1:parent:parent:parent:name = XYZAdd a hidden (admin only) calculated field to the grandchild/great-grandchild tasks with the correct parent IDIF(ISBL...

Can you use the get/pick() function? also - try to first set a variable to {{28.`DE:....} that would be the "eval" step      

Hi Niels what would trigger your scenario? the task structure is ALWAYS only 2 levels deep? how is the parent task to operate on identified?what does the scenario do - create the project and do the cleanup - or is this cleanup while the project is inflight?  

I think @Lawson02's answer is elegant and simple. By converting the date value to a timestamp, there is no need to sort/reverse since we're now in math-land and can use max/min etc. Added bonus, if you go from a true date field (ie not a text field) you avoid timezone headaches by converting to a ti...

Personally I don't like the cloning to prod approach much, instead I export the JSON, import and the re-set the connections/hooks. In that case I keep the same hook. If you clone - probably cleaner to create a new one, albeit with the caveat you mentioned.

Hi @TraKill I doubt this is what you'll want: Hiding an option hides it for wherever this field is used... in ANY other form instances on any other object.    Instead, you may want to implement this as an external lookup where the lookup pings a Fusion scenario. can you share more specifics of how y...

Hi @YaadhavanRa    Both methods make the same call. If the response is true it was accepted and you can expect the callback to your webhook.   However - the callback is just an XMLdocument - you have to parse it: it includes the download URL to the generated file.    In other words webhookparse XMLH...

Hi @Eric_D_Miller  To test: Does the upload of file 87 work of you hardcode a filename?  If it works there the filename has some sort of invisible character - you could cleanup the filename with the regexp module.

Unless you make a Fusion call to compose what you want to return, the calculated field is the way (smart!) even if you use fusion, we can't return but a single string node per results item (ie cannot return ID + name and only display name).   I hope this limitation is addressed at some point