Does Make Changes to a Thing not work on custom states?

matt71 · 2024-10-05T02:32:25.630Z

I want to make changes to individual fields inside of a custom state, which is of type Example (for example ). I tried to Make Changes to a Thing, and select the custom state as the thing. But alas, no changes were made. Should I assume then, that Make Changes to a Thing only works on DB objects and not custom states?

@keith maybe this is a job for Floppy (a plugin I’ve heard about, but haven’t yet fully explored?)

p.s. If helpful, the reason I’m trying to do this is because I have data coming in via API that’s the same schema as my Example data type. However, Bubble doesn’t see them as equivalent. Make Changes to a Thing was my attempt to assign the values of the API call to the custom state.

boston85719 · 2024-10-05T04:41:41.594Z

matt71:

Should I assume then, that Make Changes to a Thing only works on DB objects and not custom states?

Yes

matt71:

Make Changes to a Thing was my attempt to assign the values of the API call to the custom state.

Use Set State action

matt71 · 2024-10-05T05:23:14.593Z

Thanks @boston85719 In my case, the API call is actually a mock API endpoint courtesy of the JSON Assistant plugin. So I’m not able to “just” set the custom state of Type A, when the mock API endpoint is of Type B. I guess I’ll just break out the Type A data type into its constituent fields, and assign the values that way…

boston85719 · 2024-10-05T05:28:11.321Z

matt71:

JSON Assistant plugin

matt71:

I guess I’ll just break out the Type A data type into its constituent fields, and assign the values that way…

Not what I would do…I would just use the plugin for all of what it is worth, which in this case is to use it to store the JSON and modify the JSON instead of bothering with custom states at all.

matt71 · 2024-10-05T15:46:51.043Z

Ack, and appreciate the nudge.

matt71 · 2024-10-06T02:33:43.131Z

@boston85719 For posterity’s sake, Toolbox offers a good way to “convert” from one data type to another. Specifically, the Javascript 2 Bubble element → Run Javascript action sends the unique ID(s) to the JS2B element, and JS2B publishes as the desired data type. As a singular item or a list.

boston85719 · 2024-10-06T03:45:51.798Z

matt71:

Run Javascript action sends the unique ID(s) to the JS2B element, and JS2B publishes as the desired data type

Yes, this is similar to how that works for URL parameters as well. It is a single item search using the unique id that takes place in the background. It is also how a Do a Search with constraint of unique id = (unique ID value), so there is no real reason to use the toolbox plugin to send the unique ID via javascript and have the javascript to bubble element ‘convert’ it to the actual DB entry unless you are needing to send the value from a reusable element to a page or another reusable element.

matt71 · 2024-10-06T04:32:31.518Z

boston85719:

there is no real reason to use the toolbox plugin to send the unique ID via javascript and have the javascript to bubble element ‘convert’ it to the actual DB entry

What about latency? Meaning, with Toolbox I could run JavaScript and ‘convert’ asynchronously without blocking the UI thread. Meanwhile, ‘Do a Search’ would block the UI thread, and create real and/or perceived latency. No?

boston85719 · 2024-10-06T09:19:20.275Z

There is no difference. Toolbox doesn’t magically convert to the thing. It performs a do a search with constraint of unique ID, the same way as do a search. Both need to request from server for the database entry.

matt71 · 2024-10-06T15:40:14.928Z

Yup, get that. Based on my testing, however, Do a Search for unique ID blocks the UI thread, while aysnc Toolbox Run Javascript does not. (Specifically, Run JavaScript async → J2SB → publish value.) Even though both, as you point out, need to make a server call for the DB entry. Anyway… appreciate the conversation as always.

boston85719 · 2024-10-06T16:30:37.082Z

matt71:

Do a Search for unique ID blocks the UI thread, while aysnc Toolbox Run Javascript does not

Okay, I think I understand what you are saying…basically if you use the do a search for thing, the user is not able to proceed until the search is complete, while the javascript approach doesn’t cause the user to need to wait for the search to complete in order to continue using the app.

matt71 · 2024-10-06T16:33:09.250Z

Yup, that’s it!

ihsanzainal84 · 2024-10-06T23:26:36.491Z

Huh? What “latency” does a single search to a state vs a plugin search have? A call to a J2B element still runs code in it’s own instance. There’s no voodoo going on.

system · 2024-12-14T02:32:31.519Z

This topic was automatically closed after 70 days. New replies are no longer allowed.