cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

Migrate away from infotables.

Migrate away from infotables.

1. What version of Thingworx are you currently running?
9.2.1


2. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
Please consider deprecating infotables and being more friendly towards generally accepted data formats, like Arrays or JSON. I seriously can't be the only one that despises the idea of parsing universal formats like a JSON response from an API to obscure data formats available only on Thingworx.

 

If I have to make an API call, show the result on the UI in readable format, and then pass the information to another system, I'll have to do JSON -> Infotable -> JSON conversion which is very tedious.

 

The suggestion/idea is: Make the UI learn to convert JSON to table formats. Granted, you need an universal structure in order to display that on the UI. Therefore, you can make the grid widgets accept only arrays of JSON objects, with each object having the same keys, which represent the table columns. This is the main backbone of the suggestion.

 

If there's any plan of releasing a Thingworx 10 version, infotables should NOT be a part of it.

3. What business value would your suggestion represent for your organization?
Enabling a more simple way of developing general IoT solutions that follow standard data types accepted by all possible external systems.

3 Comments
olivierlp
Community Manager
Status changed to: Acknowledged

Thank you @RD_10077105 for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

atiwari-4
12-Amethyst
Status changed to: No Plans to Implement
 
RD_10077105
7-Bedrock

@atiwari-4 is there any specific reason why this is not considered for implementation? Can you offer some reasons why the team views infotables as appropriate data storing structures?