Skip to main content
Anonymous
January 23, 2017
Question

Issue on QueryPropertyHistory

  • January 23, 2017
  • 9 replies
  • 5173 views

When I use QueryPropertyHistory and increase the time period (change the End Time) some fields returned are empty, but before these values were present

9 replies

jkaczynski1-Visitor
1-Visitor
January 23, 2017

Hello Dimitri,

It is a mashup, as far as I see. Could you test this service from Composer and check the result - to make sure that it's not an error caused by browser caching. What version of Thingworx do you use (H2, Neo4j, PostgreSQL)? Please provide some information that could help to replicate this behavior. Do you perform query to get data stored in a ValueStream?

Regards,

J.

Anonymous
January 24, 2017

Hi Jakub,

Yes , It is a Mashup and I used this inside the Composer (View Mashup).

The version of Thinworx that I used is 7.2.0-b155 Neo4j.

I used  the standard service like QueryPropertyHustory, in the following picture the service used

supandey5-Regular Member
5-Regular Member
January 24, 2017

Dimitri, I have seen this behaviour but the strange part is that for me the entries became available again after few refreshes. Could you check the HomeMashup of this ValueStream or if you Test this service directly in the ValueStream thing to see if the data is still there?

ttielebein5-Regular Member
5-Regular Member
January 24, 2017

When do you update your properties? In Neo4J, there is very likely the chance that if you are updating your properties while you are trying to load the mashup, this would be the result. You would diagnose this by seeing if there are deadlocks in the thread dumps (try using jstack).

Hope this helps!

Tori

    Terms & ConditionsAccessibility statement