If I setup a global variable named my var for example, with a value of foo, and then try to use it, it does not render properly when sending a request.
I think this is fine, and doesn’t necessarily need to be fixed, however if this is intended behaviour, it should be documented somewhere, as it can be very confusing
Thank you for your suggestion. We may consider adding tooltips to discourage users from using variable names with spaces.
Hi!
We have encountered a similar issue. We saved a variable which has underscores in it’s name, e.g:
RES2_TC033_Registration_referenceId
but when we use it as a query param, Apidog adds extra url encodings at the start and end of the value together with
Here the value of the referenceId param should be : CCSC2RES2TC033referenceId1706013643
and not: [%22CCSC2RES2TC033referenceId1706013643%22]
so imho it’s not just spaces that are not working in variable names, but it seems other characters can break it as well.
Karan Can you please check and provide feedback if this will be fixed in the future, or seen as a known limitation?
We have quite a lot of tests imported from postman which break because of this issue in Apidog, and it would be nice to know wheter we should update them or rater wait for a fix for the tool. Thanks! 
How is this value set, is it from the pre-processors?
The value may be assigned as an array instead of being set as an array element.
hmm I double checked it, you are correct it is set as an array, so it’s not an issue. Sorry for the false alarm
