How do I handle optional query parameter?
I have a button that populates a query parameter only on click . I have a variable with default value null that gets specific value "A " when the button is clicked which will be used as a query parameter in the API request . How do I make this query parameter optional so that when the button is not clicked this parameter is omitted in the request URL ? @Erik Beuschau Do you have a timeline for the new version of APIs ? Additionally , how would you suggest going about putting together a marketplace -type search ? An example would be an auto marketplace , where the price , make , model , year , mileage etc are all optional in the API query ? Are you saying we 'd need 10 's of different API calls depending on what 's been selected /filtered by the user ? Timelines often change π But we are testing internally atm , and hope to start testing with heroes in a week or two . Depending on feedback , we will roll them out for everyone shortly after π€ If you have a lot of different (optional ) filters , I think the better option for now is to not use query parameters in the API dialog , and just embed them directly in the url using a formula . In that formula , you can handle the optional logic and only include the filters needed π1Thanks , Erik . That 's totally understandable on timelines ! I watched a couple videos (one of yours , I think ! ) on adding querys to a url with formulas , but I 'm not sure how to get that to actually filter the info on the page . Does the API grab all records and then the url query filters it down ? Or does the url query somehow get passed to the API ?
