Forum Discussion
Rebuild this data combination message
Ok, if this were a SQL datasource, you could get around it by using Value.NativeQuery; but it isn't.
Bear with me, because my next suggestion sounds totally stupid, but it might work. Prior to your 'Source' step, try pulling the string out of the parameter, and THEN passing it to the API call.
Something like:
this_campaign = CampaignId
and then refer to this_campaign instead of the parameter directly.
My thinking here is that the engine is nesting your outer query into your inner query, which isn't allowed, so we're forcing it to evaluate first before passing the evaluated value into the API call.
No joy. Still encountering the same error.
I ran across this in the forums...
The actual question and answer aren't the interesting part. There is an anonymous answer (Message 26)
They indicate that in order for multiple calls to Web.Contents to function correctly, they must be done in the SAME query. I assume that your source step for campaigns references another query that also makes a web.contents call to get the campaign IDs, which you are then iterating through to get the people.
Try making both calls to Web.Contents in the same query, and breaking the data into two tables AFTER you've done all of the API calls.
the easiest way, I think, would be to do all of the calls and leave the people in the unexpanded column format, create 2 more queries referencing the first, in the one, keep the unexpanded people column, and expand that, and in the other drop the column and keep the campaigns.
If it STILL doesn't work, try taking the steps of the custom function, and putting them directly inline in the single query, and see if that works.