Skip to main content
A
Anonymous
October 25, 2016
Question

INFOTABLE Properties - why can I sometimes not delete rows?

  • October 25, 2016
  • 2 replies
  • 2902 views

Sometimes, with an infotable property, when I am editing its values manually in Composer, I cannot delete rows, as in there is no option to select a row to use the delete button with.

I used to think that this was due to the table's datashape not having a primary key, but that is not the case as I just proved to myself.

Is this a Composer bug? Or am I missing something? Here is an example of a Thing with a property Versions using a datashape that has a primary key.

Capture.PNG

2 replies

T
ttielebein5-Regular Member
5-Regular Member
October 26, 2016

Could be a bug. What version of ThingWorx are you using?

A
Anonymous
October 26, 2016

Good point, I always forget to include that

This is on 7.0.3, but I have seen in off an off throughout many version 4.x and up. I will try this on 7.2.3 here sometime soon and report back.

More info: This DataShape is defined in XML but imported as a part of an extension package. I did clone the DataShape, make a new property with that, and it has the same issue, so this is likely not relevant information.

T
ttielebein5-Regular Member
5-Regular Member
October 26, 2016

I can't seem to reproduce it. I created a thing with an Infotable property, assigned it a datashape with a string field, and set and deleted entries in this infotable. Everything seemed to work as expected in 7.0.3, 7.1.0, and 7.2.3. Perhaps the issue is only intermittent for you? Otherwise, what kinds of fields are in your datashape?

C
CarlesColl1-Visitor
1-Visitor
October 26, 2016

The bug it's there, but as it doesn't affects customers I've never reported back to Support What I usually do to overpass it it's open browser developer tools, inspect the checkbox HTML and set add checked property on the checkbox tag

A
Anonymous
October 27, 2016

Nice find. I know they fixed a lot of that sort of thing around 7.1 or 7.2, things size and wrap nicer, so I am glad it was on their radar.

Terms & ConditionsAccessibility statement