problem when using dpSetTimed with null time to modify configs

[leoknipp]

Hello,

the modification of configs is possible with one of the dpSet-functions.
You probably also know that the function dpSetTimed() or dpSetTimedWait() with the null time (1970.01.01 00:00:00.000) can be used to modify the settings for a config.

This special feature can be used to avoid an increasing number of entries in the configuration history.

Please note that this is only allowed and only necessary for the configs _alert_hdl and _alert_class.
The other configs (e.g. _address, _default, _distrib, ....) do not have a configuration history. In the configuration history only the current configuration is saved for those configs.

For all other configs (except _alert_hdl and _alert_class) you have to use dpSet() or dpSetWait() to avoid problems with the RAIMA-database.


This limitation does not apply to the config original value (_original) and correction value (_corr). As these configs do not have configuration settings like the other ones the dpSetTimed()-/dpSetTimedWait()-function can be used to set a value for a specific time.

Best Regards
Leopold Knipp
Senior Support Specialist