Alarm Journal not working on every client

Ignition
1

Hello to everyone,
I have a problem with the journal component.
I use that inside three different scada projects. Same alarm journal and same components. I noticed that if I place it inside one of the three projects this will not work. The only way to work is to eliminiate the expression link inside the end date property (which is now(500))

2

In order to explain better the problem I'm attaching two screenshot:

  • The first one is made inside the Ignition designer;

Immagine 2023-07-26 090721
Immagine 2023-07-26 0907211405×849 89.6 KB

  • The second one is made on a vision client;

Immagine 2023-07-26 090833
Immagine 2023-07-26 0908331824×906 54.1 KB

I cant understand why this is happening (and only with this scada)

3

Custom SQL directly in a binding or script?

By default, Vision clients can't run such SQL, as it is a security hole. You can enable "Legacy DB" permissions in the project properties if you absolutely must. But the correct answer is to use Named Queries (with value parameters, if necessary). Named Queries do not expose the security hole as long as you do not use QueryString parameters.

4

Even with "Legacy DB" permissions, I have issue to show the alarms. I had to swap the Alarm Journal Table with the Alarm Status Table.