Empty dynamic value as null?

Need help APIs
1

Hello, I am using the API connector to connect to my website’s WooCommerce REST API and using it to show, edit, and update orders. In my body, I have added JSON object to set billing and shipping information, changing each of the key’s value to dynamic using <>.

However, I have some optional fields here such as billing and shipping street address 2 which can be left empty. However, whenever this field is empty the value is set to NULL. How can I set up my API or perhaps my fields/workflow to pass an empty value?

Any help would be appreciated. Thank you!
Wallace

2 Likes
2

I also have the same problem.

3

I’m having the same issue. When I submit an empty value, Bubble sends “null” which would not normally be a big deal, but when we view the values, it replaces the placeholder text with “null”. Any ideas, fixes or solutions would be hepful!

4

In bubble terms, null is another way of defining empty

5

Hello to all,
any update on that topic ?

6

Had same issue and could not find solution. But here is what i done. Instead of putting key value inside double quote i kept it without double quote, so my body from
“url”:"" changed to “url”:

now in case if blank
i returned as “”
in case of domain
i returned as “domain.com”

7

I got the same problem as well. Any solution?

8

I’m having this same issue.

Really need a way for Bubble to return an empty value instead of the word ‘null’

1 Like
9

I found a semi solution for this which stops the word ‘null’ showing up in templates etc.

If you use the :defaulting to operator and then apply a arbitrary text of a space, you shouldn’t see the word ‘null’ when no data is available.

Here’s how I set mine up…

Screenshot 2021-12-23 at 15.09.53
Screenshot 2021-12-23 at 15.09.53720×514 56.4 KB

Hope that might help someone else with the same issue!

10

Thanks for this! Solved my problem.

1 Like
11


This video might help
Credit to Nigel Godfrey