[šŸŒŸ New Features: Ultra-Deep Drill] JSON Assistant Plugin: Your Solution to Complex JSON & API Data in Bubble

Showcase Plugins
170

Hello.

Iā€™m working on a project in which the Backend is decoupled from Bubble (they only use Bubble for the frontend), so there are many APIs.

Many of these APIs make modifications to the database, with a POST type API call, but since we do not know which parameter the user can modify, we are creating the entire JSON with customs states, which makes it inefficient.

Additionally, once we modify something, we have to refresh the page, since otherwise the information that is being displayed with a Get type API call would not be updated.

Anyway. Would this plugin help me make workflows more efficient, but above all to not have to constantly refresh the page and make it faster?

Thank you so much.

1 Like
171

Hello @javier.arce,
I trust youā€™re doing well.

It appears this plugin is precisely what youā€™ve been searching for.

You can input the ā€˜Raw Body Textā€™ of the API into the JSONata element, which allows for easy modification of each segment. You can see how it works here

In this challenge, itā€™s unnecessary to utilize Post/Get APIs for every modification since you can employ the updated JSON from the elementā€™s state. Additionally, browser storage can be used to retain data and synchronize with the actual database less frequently.

Please inform us if you have additional questions or encounter any challenges while implementing the plugin.

172

Hello!

I started today using the plugin, it works fine but gives me a error right now and I donā€™t know where to start looking:

The plugin JSON Assistant / element { } JSON Extractor threw the following error: TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at Function.from ()
    at array_from (https://*********.bubbleapps.io/package/run_debug_js/4305cc1d11bf4a2942c5985b56bcd374dccc5da9eed49240125401df31b0ff16/xfalse/x29/run_debug.js:115:133512) (please report this to the plugin author)
1 Like
173

Hello @martijntenpas,
I hope you are well.

Could you please provide more details about when you encounter this error? Does it occur consistently or only in certain scenarios?

174

How can we specify which fields to get for Bubble Thing to JSON?
Letā€™s say I only want to return specific fields for the json.

1 Like
175

Hey mate, just having an issue with the plugin.

I upload a file, convert it with Get Json from CSV then pass it to Jsonata which converts it into a bubble thing.

This works fine when I have multiple rows in the csv however strangley when there is only a single item in the CSV it does not return any Things.

Output and Outputlist is as expected

1 Like
176

Hello @shu.teopengco,

I trust youā€™re doing well.

The plugin lacks this feature; however, have you attempted to use the format as text method and construct the JSON with the custom fields?

Please inform me if you require further assistance with this approach.

177

Hey mate,

Could you please share an example of the output JSON of that CSV with single item?
It may need to add [ ] to make it an array just like when there are multiple items.

1 Like
178

Hi @NoCodeDataArtisan. Firstly, what an awesome plugin.

When going from a Bubble object to JSON, is there a way to use the field names as I currently have them in the database?

1 Like
179

Hello @psten00,

Thank you for your kindness :heart_eyes:

Actually, the key names are generated by Bubble, and they are a combination of the first name you select for the field and its type.

180

@NoCodeDataArtisan 5 Stars! Love the plugin so far. Been playing with it for a couple of hours and have put together the best shopping cart, without needing to touch the database until the user is ready to payā€¦love it so far and Iā€™ve only scratched the surface.

1 Like
181

Thank you so much for the 5-star review! :star_struck:

Iā€™m thrilled to hear that youā€™re loving the plugin and finding it useful for building your shopping cart.

If you have any questions or want to explore more features, Iā€™m here to help.

Keep up the amazing work! :+1:

1 Like
182

I donā€™t know if this is a bug or a function of JSON. When I have a Key Value Pair, where the value is of type number and it is zero, the JSON extractor shows the value as empty in the debugger, and if I extract that value, it comes into the database as empty.

Is it possible to have 0 in JSON? Or is this an issue of how Bubble is treating the JSON?

I would suppose a work around is to set the number to 0 for database save if the value from the extractor is empty, but Iā€™d really like to have it as 0 instead of empty if possible.

1 Like
183

Actually, there shouldnā€™t be any issue when you insert a value of zero in JSON.

Are you using the JSON Extractor or the JSONata element?

185

Iā€™m using both the extractor and JSONata

For the JSONata the value shows as 0, but for extractor it shows as empty.

JSON Extractor Setup
JSON Extractor

JSONator
JSONator1422Ɨ236 34.2 KB

1 Like
186

Thank you for clarifying the issue; it has greatly assisted us in resolving it.

We have released a new version of the plugin where the bug related to zero values in the JSON Extractor element has been addressed.

Please upgrade to the latest version of the plugin and inform us of the results.

187

@NoCodeDataArtisan

Iā€™m trying to setup the plugin, but Iā€™ve been unsuccessful so far. Specifically, I used the Things to JSON action to create some JSON output. I then followed the steps in the YT video to setup Bubble-type data retrieval.

The debugger is throwing the following error for both JSON Extractor and JSONata: ā€œJSON Extractor threw the following error: Error: Expected a string, but got an object (original data: [25,50]. (please report this to the plugin author).ā€

This suggests that the Things to JSON action is generating JSON that the plugin itself canā€™t process? In particular, I have a field thatā€™s a list of numbers, and Things to JSON is outputting the following in JSON: ā€œdenomination_list_numberā€:[25,50].

@NoCodeDataArtisan: I believe Iā€™ve found and fixed the issue. Specifically, denomination_list_number was detected as type=text when I did the manual API setup. Once I changed to type=number and reinitialized, everything appears to be good. Sorry to bombard you with forum posts and DMs! :wink:

1 Like
188

Hello @matt71,

I hope youā€™re doing well.

The issue might stem from the data type youā€™ve designated in the API call.

When assigning a list of numbers as the value for a key in JSON, the correct format is:

 "denomination_list_number":[25,50]

The error suggests that the data type for this field was set as text rather than a list of numbers. To ensure the JSON is detected correctly, itā€™s best to use the exact output as the input for the ā€˜Manually enter the API responseā€™ option.

189

@NoCodeDataArtisan Yup, I just diagnosed the same. Once I updated the field assignment to type=number in the API call, everything was good. Thanks, and onwards!

1 Like
190

Thatā€™s wonderful to hear.

Please donā€™t hesitate to contact us again if you encounter any challenges or issues. We are always here to assist you.

Your support means a great deal to us, and we would be thrilled if you could spare a moment to leave a review for the plugin and share your experience with others.