Community Tip - You can change your system assigned username to something more personal in your community settings. X
How can we store a service output in DataTable insted of InfoTble in Thingworx.
Solved! Go to Solution.
Hi @SM_10230689
I would say it would depend on your use case. Kindly refer to the best practice below
In short, if your data is on a row-by-row basis update or change, and easy to look up I would recommend a data table, But if your data relatively doesn't have many rows, doesn't need to look up on specific row and logically easier to relate it with the specific thing then I would recommend an infotable
From my experience don't use infotable if it contains more than 500 rows, and use databaseThing to connect to database if your rows size is more than 50000. Otherwise it will cause a performance issues on ThingWorx.
Thanks
Hi @SM_10230689
I would say it would depend on your use case. Kindly refer to the best practice below
In short, if your data is on a row-by-row basis update or change, and easy to look up I would recommend a data table, But if your data relatively doesn't have many rows, doesn't need to look up on specific row and logically easier to relate it with the specific thing then I would recommend an infotable
From my experience don't use infotable if it contains more than 500 rows, and use databaseThing to connect to database if your rows size is more than 50000. Otherwise it will cause a performance issues on ThingWorx.
Thanks