Handlebar template for tableID

I am trying to reference a dataTable using handlebar template in my workflow, ideally i want the workflow to loop through a bunch of tables. I cant seem to make the template work, i just get an error table not found, as shown below the name is valid, or is there a different “ID” i need?:

Hey @Josh_Bell,

The ID you need is the ID of the data table, not the name.

The best way to get this is to go to the data table, and you can find the ID in the URL:

Optionally, you can use a Losant API Node with the Data Tables: Get method to get a list of data tables that the application has.

Could you tell me a little more about why you’re looking to loop through multiple data tables? I’d love to learn more about your use case and maybe help you a little more.

Please let me know if this works for you.

Thank you,

Thanks for that, i figured it would be something to do with the name vs the ID of the table i just didn’t know where to find the ID. Is there a way to return the name of the table with the “Table get rows” node?
The reason for the loop is to do data analysis on multiple tables in the same workflow.
I have devices located in different blocks of a building complex reporting states to tables that reflect the block they are in, ie D-block devices report state to the D-block table, A-block to the A-block table etc. This workflow looks up the individual block table and does some time based averaging (as per my feature request) on the data and returns the results to a combined results table, i currently do it with a delay but it doesn’t scale well when I want to add more blocks in the future:


Thanks so much for sharing this information!

Is there a way to return the name of the table with the “Table get rows” node?

Are you looking to use an ID of a table to get the rows, and have the node get the rows, and then return both the result of the node & the name of the table?



I solved it by creating another table that contains the name and ID of the tables I want to look-up.

It would be good if when you used the “table get rows” node it returned the ID and name of the table as well just so it was in the payload somewhere you could reference it later.