[bug?] When a Memory Document Tag or Dataset value is modified from the designer Tag Browser, the Timestamp is not updated

Ignition
1

Ignition 8.1.39
@PGriffith

When a Memory Document Tag or Memory Dataset value is modified from the designer Tag Browser, the Timestamp is not updated.

is it bug or the expected behavior ?

With the same tags, writing a value with system.tag.writeBlocking, update the Timestamp.

2

This appears to be an intentional optimization, where only the single part that's modified is actually sent over the wire from the designer, and then the dataset on the gateway side can be updated in-place instead of having to construct an entire new dataset.

3

Ok I see. I wanted to use Timesramp property to detect some change on dataset and document tags...

4

But this is a designer optimization. Are you seeing this at runtime?