more quick actions
minimize quick actions
Hello all,
I am facing a problem in data export. I configured 10 exports with log lists and trends. I generated these data to excel files after the configuration. But once i restarted PcVue, only 1 export with 1 loglist is there. The same is reflected on "DataExportsConf.xml". I tried to replace with old "DataExportsConf.xml" but it is not working and after restart it is again changing to the 1 export with 1 loglist. Attachment have the 2 different "DataExportsConf.xml" before restart and after restart.
Thank You
Tijo
Posted : 04/04/2018 5:12 pm
Hello,
This is a known issue with 11.2 Update 5.
It has been fixed but there is another issue to fix now.
The file name of the Data export is not saved!
So after restart the only possibility to generate is to use scada basic instruction in which we can set the file name:
res = Export("GENERATE", "Export11","","Export11.xlsx");
Posted : 04/04/2018 7:43 pm
What is the best solution? Moving to lower version is good?
Posted : 04/04/2018 8:05 pm
Hi,
We are aware of these issues and an Info bug message will be sent later today with the exact status.
At that stage, we do not know exactly when these 2 regressions were introduced, so it is not possible to recommend a precise build which is affected by none of these 2 issues (but for sure one before the 11.2.06063 aka the update 5).
More to come tomorrow after more investigations in the change history.
Sorry for the inconvenience, we are investigating and setting up a plan as diligently as possible.
Regards
Posted : 04/04/2018 8:50 pm
Thank you Benoît and Ludovic
Please advice me, which 11.2 version with data export is more stable for commissioning onsite.
Regards
Tijo Mathew
Posted : 05/04/2018 1:24 pm
Hi,
At that stage, we are still investigating to understand when exactly the main issue was introduced (loss of all config except 1 data export).
If you can wait until tomorrow for the answer, we should be able to give you an accurate answer.
Regards
Posted : 05/04/2018 9:34 pm
Hi Tijo,
Apparently the changeset that introduced this regression is the number 22257 from 17/11/2017
So, the version 11.2 06060 should not have this issue.
So, we are going to release a new update soon fixing this issue. If you can wait a bit...
Nico
Posted : 09/04/2018 7:23 am