Summary
The user is facing an issue with passing the uid from a parent stream to a child stream in the declarative source setup. The parameterized request is not injecting the actual uid value correctly, resulting in a literal representation in the URL.
Question
This might be a dumb question but…
I’m facing an issue with a parent-child stream configuration in the declarative source setup. I have a parent stream (Clients) and a child stream (Properties). I need to pass the uid from the parent Clients stream into the child Properties stream as a query parameter.
In the Parameterized Requests section, I’m using {{ parent['uid'] }} as the value list and uid as the Current Parameter Value Identifier. However, when I test the configuration, the request URL encodes the query parameter incorrectly, and instead of injecting the actual uid from the parent, it ends up as a literal {{ parent['uid'] }} in the URL.
Here’s an example of the generated request:
T
<https://dev.test.io:123/api/v1/properties?uid=%7B%7B+parent%5B%27uid%27%5D+%7D%7D>```
Could you please confirm if `{{ parent['uid'] }}` is the correct syntax for injecting a parent stream value, or suggest the correct approach to pass the `uid` from the parent stream into the child stream’s request?
Thanks in advance for your help!
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1728581338178349) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
["parent-child-stream", "parameterized-requests", "uid", "connector"]
</sub>