Yes, here is my SOP process. 1. Make a "count" call, where the query matches your final query2. Create a variable, I call it maxResults usually3. Place a repeater module that starts at 0, in the repeats put ciel({count}/{maxResults}), and then in steps, put maxResults4. Place your "real" query, mapp...

As far as I know, yes, though to be fair I just use the custom API module 95% of the time regardless, so it's possible I'm wrong.

This is called pagination. Essentially, you have to specify how many records you want, and where the first item you want returned in the total list of returns is, by including $$FIRST={the first record you want from the total list) and $$LIMIT, which dictates how many results you want in your respon...

Tested, that should work.

I don't think the portfolio ID triggers a webhook message.  For this situation, probably the easiest thing to do would be to add a calculated field that's equal to portfolioID, and make sure that field is tracked, then use that field to trigger Fusion.

I'm unable to test this, but does formatDate(parseDate(10/1/2023;DD/MM/YYYY);MM-YYYY) work?

get({array};2)

I just tested it and verified it works. Is the Workfront account that's generating the webhook the same as the one that you're using to edit in Workfront?

It should work. There are a couple of default fields that won't trigger a webhook and this is my standard workaround for that.

Yes, this is an option, but it is wildly more complicated, and my recommendation would be to use a calculated field with a watch events triggering off of that custom field, similar to my other comment. There are several negatives to doing what Workfront is recommending, and I have done this before, ...