Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I'm trying to configure the "new" tHttpClient component (since the tFileFetch is depreciated), and I have an issue to configure a dynamic value for the attachement name.
I try the following values to retrieve the input "tmpFileName" field, but none of them work:
The downloaded file use the value specified in the field, with the dot and the braces, for the file name, but never the value provided in the associated field.
Do I use a wrong method, or is it the component which does not allow such an option?
Talend Studio R2026-06
Hi @FrancoisP_CH,
Thank you for reaching to Qlik community support.
In Talend Studio R2026‑06, the new tHttpClient component does not support row expressions in the “Attachment name” field. The field only accepts literal values or context variables, so expressions such as {.input.tmpFileName} or row5.tmpFileName are interpreted as static text.
To achieve dynamic file naming, you can:
1.Assign the row value to a context variable before calling tHttpClient and use that variable in the Attachment name field.
2. Alternatively, download the file with a fixed name and then rename it afterward using tFileRename or tFileCopy.
This is a known limitation compared to the older tFileFetch component
Hi @FrancoisP_CH,
Thank you for reaching to Qlik community support.
In Talend Studio R2026‑06, the new tHttpClient component does not support row expressions in the “Attachment name” field. The field only accepts literal values or context variables, so expressions such as {.input.tmpFileName} or row5.tmpFileName are interpreted as static text.
To achieve dynamic file naming, you can:
1.Assign the row value to a context variable before calling tHttpClient and use that variable in the Attachment name field.
2. Alternatively, download the file with a fixed name and then rename it afterward using tFileRename or tFileCopy.
This is a known limitation compared to the older tFileFetch component
Thanks for the answer. I use a tFileCopy after the tHTTPClient and it works fine.