Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

lookup row on tRESTRequest

Hi all,

I have a REST job that is passed with 10 parameters that get manipulated and return a REST response at the end.
I am having problems with a lookup row within my job, since the lookup involves using one of the passed parameters from the REST, but the lookup component seems to start immediately once the REST is called, giving a null pointer exception and causing the job to throw an error. How can I set the lookup row to perform only once the job is running, and not once the REST is called?

Attached is a screenshot of my job layout, highlighting the concerned components in red boxes.

0683p000009MH43.png

Best regards,
Junmil

Labels (2)
1 Reply
Anonymous
Not applicable
Author

Hi Junmmil 

The lookup data are always loaded before the main data. To resolve this issue, you just need to use a tFlowToIterate to iterate each request.
tRestRequest--main--tFlowToIterate--iterate--tFixedFlowInput--main--tFilterRow.......

With this job, you are able to access the input parameter in the lookup flow.
tFixedFlowInput: get the current request fields.