Versions Compared

Old Version 70

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version Current

changes.mady.by.user Gill Houghton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

Writing historical events directly to tag is required if there are:

  • Tag Events scripts that fire when applicable
  • Alarms that are triggered when applicable
  • Reference tags used to indirectly reference MQTT Engine tags


Note

If using Postgres as the Historian, setting the following 'extra connection properties' in the DB connection settings will cause all data that can be stored to be stored in the historian. Without these connection properties, full batches of data will be tossed if duplicates are found in any batch.

Code Block
autosave=always;cleanupSavepoints=true




Anchor
writetodatabase
writetodatabase
Writing historical events directly to the database, via the Historian, bypassing the tag

...

Edge Client

The Edge side client can should publish historic data either in-order (synchronously) or asynchronously.

Tip

If you are using MQTT Transmission as the Edge side client, under the MQTT Transmission Settings for your transmitter, navigate to the History Settings to disable the In-Order History configuration parameter. Enabling the In-Order History for MQTT Transmission is unnecessary and will result in a waste of resources. 



Anchor
writetotag
writetotag
Writing historical events directly to tags

...