Hello Marty,
We use SQL data sources and then Meta Sources to scale the raw data into meaningful data. To avoid Mango creating data points while communication was lost from the data logger we have Mango set to read on a timestamp change only.

On the SQL data source we have a data point just for the timestamp, the other data points use a time override column name and on the meta source we use the timestamp data point for the context update.

Of course this will only work if your logging device creates its own timestamp or your SQL database records the date and time of the data insertion into the table.

I hope this helps

Cheers

Brian

Hello Terry,
Thank you for you response. This will let me continue with the upgrade. I am sure we can work with the unique email address point. It will just need to make sure I get a separate contact address for each user and explain to the customer it is for password recovery.

Thank you for your help and I hope you all had a happy Thanksgiving.

Cheers

Brian

Hello Phil,
I just wanted to thank you. The point links worked great once I understood how to use them and the scripting. This is how I did it in case anyone else wants to know:

I have an SQL data source that needs to be read when the data comes in, not on a set interval and I need to use the data's own timestamp.

My data source uses this select statement:

SELECT * FROM staging_all where logger_id=1 and flag=0 order by date asc limit 1;

To trigger the reading of each row I set up a point link as follows:

I have a source data point that is set a a virtual sinusoidal that is going between -1 and +1 every 10 seconds.

I have a target data point set up as a modify table only point.

The point link uses the following one line script:

  if (source.value >0) return '(1)'; return '(0)';

I needed this line because the target data point was an alphanumeric data point.

My target point has this script:

  UPDATE staging_all SET flag=? WHERE logger_id=1 AND flag=0 ORDER BY date ASC LIMIT 1;

Now the data point that modifies the staging table gets a trigger (1) several times a minute and that causes my data rows to be read one at a time until they are all marked as (1).

Thank you for pointing me in the right direction.

Hello Shubham,
We run a system with many users and limit what the users can access on the menu. We also have to isolate the custom pages from one user to the other. Matt is correct, you will have to edit the Menu permissions and the Page permissions to limit what each user is able to see and do.

I will show you what we have set up. It might not be the best way to do it but it works for us. Any advice on a better way to do this would be greatly appreciated. :)

1. Create the user and give the user a unique role.
   

2. In the settings / permissions remove User from all items you do not want the average user to access. Everything else will still be accessible by the superadmin as default.
   

3. Use the Edit Menu function to remove set the appropriate permission for your user. Some items such as the Help menu we have left as User:
   

4. other items we remove the User account from the permissions such as the API Docs menu item:
   

5. Those items that are user specific such as the custom pages, we set the unique user role:
   

I hope this helps you get it set up the way you wish.

Remember to click Save in all the right places.

Cheers

Brian

Hello cwangv,
If you are just browsing the list from the drop down of the Point Properties - Unit values then you will not see some of the units available. I found that if you type the ones you need such as mm, cm kW and kWh and click save, the point will save with proper validation. %RH is not available for validation, but % is available. The drop down list is not the full list of units available.

To use non standard units, you would need to go to the Text Renderer Properties and untick "use unit symbol as suffix". Then you can enter in your desired text in the Suffix value.

Cheers
Brian

Hello,
Since our recent Excel Reports Module upgrades from 3.6.2 to 3.7.0, all of our scheduled Excel reports are not running automatically. They were working fine before the upgrades. I can run the reports manually but the CRON schedule is not working.

I have recreated the schedule from scratch on our test report but is is not running either. There is also nothing showing up in the ma.log file.

I have noticed that when I click the gear icon next to the report, I get the choices to copy, delete, run or schedule. When selecting schedule the only option there is to set the time period. I have always used the actual report template set up to set the schedule so am not sure if the CRON pattern choice was available from the schedule option of the gear icon.

I am wondering if the schedule option from the gear icon does not allow setting the CRON pattern for the schedule, has the scheduling been dropped by accident?

I am eagerly looking forward to your response.

Cheers,

Brian

Hello Terry,
Thank you very much, I just got a chance to update the modules and test the scheduling.
Working great now.

Cheers

Brian

@MattFox Hello Matt,
Thank you very much for spelling that out to me.
Here's the rub though.

I am trying to use a timestamp to update an integer. So on validation I got this message:

Setting point 0100raw - 0100-zflag to 2024-03-14 09:20:00.0 @ 12 Apr 2024 07:54:01 UTC

What I really need is the parameter to set a 1 when the timestamp updates.
In the old point links I had a simple line,

Return '(1)';

So I tried something actually quite simple once you know. I left the timestamp as the update context and used this script:

target.set('(1)')

I assumed that the example Phil put on the forum all those years ago required me to assign the target and source point in the script code.

Sometime I can't see the forest for the trees.

So HUGE THANKS Matt. I can now get my system running and I now know how to take it into Mango 4 hopefully.

Cheers
Brian