I am also seeing it not update after sorting via listshifter
Table appears to filter once on a state change but then does not filter again.
For example if you set it up to filter through a radio button it will filter the first time the radio button changes but not after that.
Working with a table element is absolutely killing my RAM. It’s only happening when directly editing / modifying the table element, but it’s crashing my page every 10 minutes or so.
Do you have the experimental features turned on for the editor? I’ve been working on tables heavily since it was released and haven’t had any crashes so far. Also what browser are you using?
Viene con muchos errores. Primero quise poner un campo de input, pero no permite editar desde el mismo lugar, aunque encontre una forma de saltar esto. Si hago un workflow en algún campo, algo tan simple como editar el mismo campo, el sistema o el debug te dice que lo hace, pero vas a la base de dato y no esta realizado el cambio.pareciera que sacaron la tabla apurada y con bastantes errores
Un desarrollo beta es funcional, aca se saco muy rapido a testeo de Q&A, tiene mas errores que cualquier otra funcion beta y eso que llevo 2 años en la plataforma
Definitely a bug with the Table element and data sources.
It won’t display any updates to its data sources. I did a simple test for it to display a list of text from a state. Debugger shows the change in Data Source values but the Table itself doesn’t show the new values. Neither does putting it in a group and resetting it work. It does show the correct values on the first data source change but fails on subsequent attempts.
How did this pass QA for a Beta release? I’ve filed a bug report.
It’ll be great if the columns can except a list so I can dynamically update them.
I already have a workaround by using RGs but it’ll be nice if the Table Element didn’t need silly workarounds for dynamic columns.
no me funciona ningún dato que venga de el row, no se guardan como estado, no se puede hacer nada con ellos .Solo sirve la tabla para mostrar datos ya creado
It’s definitely a bug because the list does reflect the change in data source but only once. Anytime I try to update the data source after that, it won’t work.
I think it’s working now:
Would be great if I could add a workflow to a row, too. Or am I just too stupid to find it?
trate de crear un flujo, pero cada vez que agrego el row no lo identifica, lo probe de varias formas y no he podido hacer que funcione
Agree, we should be able to trigger workflow by clicking on a row - all my RG tables work like this and I wouldn’t want to lose that feature.
@kate.mcnally - Hi, is this in beta or has it completed beta? Many t hanks!
I wouldn’t care as much if bubble properly converted my pages to the new editor. When I do it, it absolutely ruins the page. Elements missing and misplaced…
just remake it entirely at this point. shouldnt’ve stayed on the old version for this long anyways
I’m quite disappointed that this thing still doesn’t solve the huge limitation of not calculating column grand totals
No entiendo cual es la logica de hacer un elemento tabla que no puedes interactuar con ella?
Also, to add what @nachodip97 said,
Remaking the page in the new responsive format is the best way to get a grasp on the new responsive engine. If it auto did everything for you, you would be more clueless as to how your page is functioning and if you had to make any changes, it would be be hard to near impossible without breaking everything.
Once I realized everything is rows and columns, everything made sense. If it didn’t operate the way I wanted to, group it into a row. If that didn’t work, reverse and group into a column.
For example, an old part of my app I don’t use anymore but is as follows;
The red squares are Column groups, and the purple square is a row group. If I didn’t have everything in a row group, it would all be straight up and down, or vice versa it would all be side to side.
It just takes some playing around, but it makes adding things/aligning things so much easier for future development, especially going from large pages to mobile views.
Good luck!