Annoying Bug with Dynamic Columns in HTTP Requests: Video Overview

Mathew I. · 2024-12-17 02:41:53.876171+00

Tiny but very annoying bug when inserting dynamic columns into HTTP requests Recorded video here:

Annoying Bug with Dynamic Columns in HTTP Requests: Video Overview | Clay

9 comments

· Sorted by Oldest

Channeled
APP
·
·
As of October 2024, there's an important requirement when using dynamic variables in HTTP API requests: you must enclose dynamic string variables in quotation marks.When using dynamic variables with /column, follow these JSON formatting rules: ** String variables must be enclosed in quotes ** Number variables don't need quotes (except for numbers with trailing zeros like "0004") * Boolean values don't need quotesIf you need to combine plain text with a dynamic column tag, first create a Formula column to combine them, then include that column (with quotes) in your body tag.For more details about this change, you can watch our explanatory video here: video Sources: HTTP API with JWT authentication | Clay University HTTP API integration overview | Clay University
Mathew I.
·
·
person
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Bruno R.
·
·
Hi Mathew, thanks for reaching out. Taking a look at this now!
Bruno R.
·
·
Mathew - Do you mind sending the link to the table so we can take a look? This will also be helpful to our engineering team to look into this issue further. https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1734417900&signature=ff4ab55580b0272380a404285e1d1d3f9d094351846501d6cff4356915c3ff51&req=dSEgF85%2FmohWX%2FMW1HO4zYTywS%2F4B5Af2BKsam%2FhVPtDqA%3D%3D%0A
Mathew I.
·
·
https://app.clay.com/workspaces/295058/workbooks/wb_MD5PyignoZJM/tables/t_UtnZnk98nasx/views/gv_bGRztNR4Mycs
Bo (.
·
·
Mathew - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Mathew I.
·
·
thanks
Daniela D.
·
·
Hey Matthew! Apologies for the delay. We’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, we will tentatively mark this as closed. Please note that I will reach out to you as soon as we receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?
👍1

Channeled
APP
·
·
As of October 2024, there's an important requirement when using dynamic variables in HTTP API requests: you must enclose dynamic string variables in quotation marks.When using dynamic variables with /column, follow these JSON formatting rules: ** String variables must be enclosed in quotes ** Number variables don't need quotes (except for numbers with trailing zeros like "0004") * Boolean values don't need quotesIf you need to combine plain text with a dynamic column tag, first create a Formula column to combine them, then include that column (with quotes) in your body tag.For more details about this change, you can watch our explanatory video here: video Sources: HTTP API with JWT authentication | Clay University HTTP API integration overview | Clay University
Mathew I.
·
·
person
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Bruno R.
·
·
Hi Mathew, thanks for reaching out. Taking a look at this now!
Bruno R.
·
·
Mathew - Do you mind sending the link to the table so we can take a look? This will also be helpful to our engineering team to look into this issue further. https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1734417900&signature=ff4ab55580b0272380a404285e1d1d3f9d094351846501d6cff4356915c3ff51&req=dSEgF85%2FmohWX%2FMW1HO4zYTywS%2F4B5Af2BKsam%2FhVPtDqA%3D%3D%0A
Mathew I.
·
·
https://app.clay.com/workspaces/295058/workbooks/wb_MD5PyignoZJM/tables/t_UtnZnk98nasx/views/gv_bGRztNR4Mycs
Bo (.
·
·
Mathew - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
Mathew I.
·
·
thanks
Daniela D.
·
·
Hey Matthew! Apologies for the delay. We’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, we will tentatively mark this as closed. Please note that I will reach out to you as soon as we receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?
👍1