Hello all,
I noticed starting with DM 1.1 the maximum alarms and the fallback minimum is set to “0” by default and when you initiate the change to the known value of 300,000 and 100,000 alarm after applying the new changes it immediately reverts to “0”
Any idea how this can be corrected and what does “0” mean in this case?
Hi Merlin,
I only found this on documentation: Configuring the SQL database settings | DataMiner Docs, which might be relevant.
It’s possible that the value you’re trying to set is not allowed by the system (?). The behavior of reverting to “0” could indicate a validation failure or a restriction on the acceptable range of values, imo.
Have you tried using the up and down arrows after entering the desired value? Sometimes, interacting with these controls can help the system recognize and validate the input. For instance, after entering “300,000,” try pressing the up arrow once and then the down arrow to see if it adjusts to the maximum allowed value automatically.
Let me know how it goes!
Kind regards,
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer (using the ✓ icon) to indicate that no further follow-up is needed?