Cannot detach default 'id' from 'get row object' block - Stuck on Local DB Export!

Questions about Thunkable Issues / Bugs
1

Hello Thunkable Community,

I’m incredibly stuck and looking for any possible workaround to proceed with exporting data from my local database.

The core issue: I am trying to retrieve all data from my SubmittedPledgeDB (local database) by looping through number of rows and using the get row object from SubmittedPledgeDB for row id [ID] block.

However, I cannot for the life of me detach the default ‘id’ block that comes connected to the for row id input. It’s causing an “incompatible connection” error because it’s a text type block trying to go into a number input. I’ve tried:

  • Dragging it far away.
  • Dragging it to the trash can.
  • Deleting the entire get row object block and dragging out a fresh one. Nothing works; it remains stubbornly stuck or the new block instance has the same issue.

This problem completely blocks my ability to loop through rows using the i (loop index) variable* as the row id.

Additional challenge: My Thunkable version/setup also does not seem to have a direct get all rows block for the local database, which would be an alternative to the loop-by-ID method.

My Goal To get all data from my SubmittedPledgeDB as a list of objects so I can then format it for CSV or Google Sheets export.

My Question to the Community:

  1. Is there any workaround or alternative method within Thunkable’s blocks to reliably “get all data” (all rows as objects) from a local database, without relying on the get row object for row id block?
  2. Has anyone else encountered this specific issue of being unable to detach the default ‘id’ block from the get row object? How did you resolve it?

I’ve spent a lot of time on this and it’s quite frustrating that a fundamental block interaction is preventing me from moving forward. My logic for the export is ready if I can just get this data.

Thank you so much for any insights or help you can provide!

image
image1920×1034 134 KB

3

Hi @dnistor02ca6p, welcome to Thunkable! :tada:

As row ID you could use the “i” variable.

Be sure to check out How to ask Great Questions v2.0, the Community Guidelines, and our Getting Started Guide to make the best of your Thunkable Community experience!

4

Thank you for the clarification! Yes, I understand that the ‘i’ variable is the correct one to use for the row ID.

However, I am facing a persistent technical issue: I cannot detach the default ‘id’ block that automatically appears connected to the ‘for row id’ input of the get row object block. This id block remains stuck, and because it’s an incompatible type (text instead of number), it physically prevents me from connecting the ‘i’ variable (or any other number block) to the ‘for row id’ input.

I have already tried:

  • Dragging the ‘id’ block away or to the trash.
  • Deleting the entire get row object block and dragging out a fresh one (the new one still has the same stuck ‘id’ issue).

Could you please provide a solution for how to detach that ‘id’ block, or advise on whether this is a known bug? If this block remains unusable, is there an alternative method to programmatically retrieve all rows from the local SubmittedPledgeDB (since I also don’t have a direct get all rows block in my version)?

Thank you for your continued help!

5

You can’t detach the “id” block. It’s a placeholder. You should be able to connect a numeric value, text value, or variable such as i to it. Are you able to share a link to your project?

7

I’ve sorted it out! It exports correctly!

Thanks!

image
image1920×1305 125 KB