Skip to main content
J
johnjosh265-Regular Member
5-Regular Member
June 4, 2021
Solved

Properties of the database thing changed even after set into read-only mode (ThingWorx 8.4.4)

  • June 4, 2021
  • 1 reply
  • 2065 views

Hi everyone,

 

I don't know why, but the properties in the database thing (INFOTABLE) are often changed and the values are often duplicated.

 

The properties have been set into read-only and persistent.

 

Is there anyone that faces the same problem?

 

Thanks.

Best answer by PaiChung

If these are infotable type properties, they may be affected by your services.

If you have services work with InfoTable properties and those properties mustn't be changed, you need to first use 'CloneInfoTable' to clone the content of the property and then use the content.

Any direct sort/filter/search etc. done with the infotable property will affect the property value.

 

Not sure if that is what you are experiencing.

1 reply

P
PaiChung22-Sapphire I
22-Sapphire I
June 4, 2021

Can you provide some more information please? Screen shot of before and after?

Also any idea of what services you are running that might affect the Database Thing?

J
johnjosh265-Regular MemberAuthor
5-Regular Member
June 6, 2021

Hello, sorry for the late reply

 

I'm sorry, I think I can't give you the actual screenshots, but I think I can "replace" them with excel examples.

 

I think the only services that affect them are the services with the sort function only.

 

The values are not changed by the services.

 

 

P
PaiChung22-Sapphire IAnswer
22-Sapphire I
June 7, 2021

If these are infotable type properties, they may be affected by your services.

If you have services work with InfoTable properties and those properties mustn't be changed, you need to first use 'CloneInfoTable' to clone the content of the property and then use the content.

Any direct sort/filter/search etc. done with the infotable property will affect the property value.

 

Not sure if that is what you are experiencing.

Terms & ConditionsAccessibility statement