Skip to main content
13-Aquamarine
November 4, 2025
Question

Query Boolean Property History Working different among things

  • November 4, 2025
  • 2 replies
  • 546 views

Hi all,

 

I am experiencing strange behavior using QueryBooleanPropertyHistory among nearly identical things.

 

If I specify start and end date I see data on both things, as expected:

JK_10744682_0-1762271775727.png

JK_10744682_1-1762271782280.png

 

 

However, if I only specify end date, on one thing I get data but on the other I do not:

JK_10744682_3-1762271880764.png

JK_10744682_4-1762271891437.png

 

Why would there be different behavior for one versus the other? The things are created identically from the same template. Version 10.0.0. 

 

2 replies

16-Pearl
November 5, 2025

Hi @JK_10744682  

 Can you take a look at the article below?

https://www.ptc.com/en/support/article/cs226000

13-Aquamarine
November 5, 2025

This does not detail my issue. It actually says the issue I am having should not occur as leaving startDate/endDate empy should result in data based off the oldestFirst property.

JK_10744682_0-1762348149464.png

 

16-Pearl
November 6, 2025

I assume that you have some filter applied in your query (which you blacked out)? If you do not have a filter - ignore the rest 😉

 

With this query filtering the issue is that TWX will

1. fetch maxItems with the start/end date settings

2. on this result it applies the query

3. result is returned

So it most likely finds 500 entries, applies your query which filters out all 500 and you are left with 0 rows. You could verify this by making maxItems very big and see if you get some results at one point.

 

https://support.ptc.com/help/thingworx/platform/r9.6/en/index.html#page/ThingWorx/Help/Composer/DataStorage/ValueStreams/UsingTheQueryPropertyHistoryService.html "What happens Post-Processing?"

13-Aquamarine
November 6, 2025

I do not use a query here, so I don't believe that is the issue 

16-Pearl
November 6, 2025

yep. should be some other issue mh