Populating the spinner with database data

[RaYzZz (Gianluca Franco)]

I just noticed you were showing your database name, I’ve hidden it

I see that you’re already using the web component to fetch the data, you’re really close to fully using Firebase with the web.
The thing is, the data you have isn’t formatted correctly, if you managed to save it properly, everything would become much simpler.

[Carlos_Alberto_Leonel]

And which format would be the most correct?
is it?

[RaYzZz (Gianluca Franco)]

Try looking at this example, it might help you understand how it works. But believe me, Tim’s guide really explains everything.

[Carlos_Alberto_Leonel]

Suppose I do it like this.

To retrieve this data in the event of an edit, can I use this same component or do I have to use another web component?

[RaYzZz (Gianluca Franco)]

[Carlos_Alberto_Leonel]

If it’s not too much to ask, can you give me an example?

[RaYzZz (Gianluca Franco)]

Have you tried following the guide?
You just need to add a hidden WebViewer and a few simple blocks.

[Carlos_Alberto_Leonel]

I’ll try following the tutorial. If I can’t, I’ll let you know here through the blocks.

[Carlos_Alberto_Leonel]

Gianluca, when using Niotron and faced difficulties using Firebase on that platform, I used the web component to register.
Since Firebase works with Kodular, I didn’t encounter any problems, so I didn’t need to use the web component to register.
I think it’s an excellent feature, but registering personal data requires some changes (updates). I read about it, but I didn’t understand how to make changes to the registration.

[RaYzZz (Gianluca Franco)]

@Carlos_Alberto_Leonel

Since Firebase works with Kodular

For saving simple tags with text, it’s perfect, but once you start working with lists and dictionaries, that’s where the problem begins.
In fact, if you look at your data, it isn’t structured, it’s just plain text.

"Produto": "[\"Arroz\", \"Feijão carioquinha\",\"Açúcar \",\"Óleo de Soja\"]"

instead of

"Produto":
[
   "Arroz",
   "Feijão carioquinha",
   "Açúcar ",
   "Óleo de Soja"
]

@Carlos_Alberto_Leonel

I read about it, but I didn’t understand how to make changes to the registration

Anyway, explain me better what you mean by this sentence.

[Carlos_Alberto_Leonel]

For Cadastro_Pesoa I used the Dictionary:

To edit the data, I used another web component:

And I used the same block to save.

before:

After:

I don’t know if what I did was right, I mean the structure, but it worked.
Now I don’t know how to do this:

using the dictionary

[RaYzZz (Gianluca Franco)]

Hi,

@Carlos_Alberto_Leonel

To edit the data, I used another web component:

You could use a single web component to perform any kind of operation, but let’s say it’s not a big problem.

---

@Carlos_Alberto_Leonel

I don’t know if what I did was right, I mean the structure, but it worked.

@Carlos_Alberto_Leonel

I’d say that’s perfectly fine,

“numero” is being treated as text, if you notice, it’s between quotes, whereas it shouldn’t be if it’s just a number. But that’s not really a problem either.

---

@Carlos_Alberto_Leonel

Now I don’t know how to do this:

using the dictionary

This is a simple list.

[Carlos_Alberto_Leonel]

Sorry Gianluca, but is that it?

[RaYzZz (Gianluca Franco)]

Yes , have you tried?

[Carlos_Alberto_Leonel]

Yes, but it overwrites another value. For example, hypermarket. When you type Villerfort, it becomes:
0: “Villerfort”
When you include another name, such as Supermercados BH, it overwrites:
0: “Supermercados BH”

I think there should be a validation event where, when entering a new supermarket, product, and brand, it would check if it already exists. For example, if supermarket “X” already exists, it would include “Y” on the next line. Or, if the user tried to enter “X” again, the app would inform them that a supermarket with that name already exists.
The Firebase component can be used to do this, but I don’t know where to start with this web component.

[Carlos_Alberto_Leonel]

I thought about doing this logic here:

[RaYzZz (Gianluca Franco)]

@Carlos_Alberto_Leonel

but it overwrites another value

Two methods:

• Get the list, save it in a variable, and send it back with the new element added.
• A list is simply a dictionary with keys (0, 1, 2, 3, 4), so you can also send a dictionary pair with the key as (last list index + 1) and the value as the item you want to add.

@Carlos_Alberto_Leonel

should be a validation event where, when entering a new supermarket, product, and brand, it would check if it already exists

For this, I think an is in list is enough to check whether the data is present.

[Carlos_Alberto_Leonel]

I think I’ll leave it as it was. I’ll leave it as it is because I don’t know how to do this using the dictionary and the web component.

[Carlos_Alberto_Leonel]

I did something like this, but it’s storing JSON text and not an actual list.

[RaYzZz (Gianluca Franco)]

Hi Carlos,

but wasn’t it enough to just do it like this?

But I don’t really prefer this method.
Unless the user is writing in a field that only they can edit, there’s a risk that other users might have different versions of the lists and end up overwriting other users’ data when they send their own.