.HISTORY.ENABLED

[Duc M Do]

​A user asked me about this report in Foxray, and after a cursory check in FoxDoc, I have no answer.

HS13274B is a COUT block. I/A version is v9.1.

Anybody care to educate this user? Thanks!

Duc

[Ricardo Abech]

Hi Duc,

This parameter is mainly for Archestra (EVO) and it records the change on the historization bit inside the Galaxy. If this was not the case with this client (they did not change anything or not using Galaxy) I suggest opening a case with GCS (Schneider Support) so we can look into it.

Thanks

Ricardo

--
You received this message because you are subscribed to the Google Groups "LimeWare foxray™" group.
To unsubscribe from this group and stop receiving emails from it, send an email to limeware-foxray+unsubscribe@googlegroups.com.
To post to this group, send email to limeware-foxray@googlegroups.com.
Visit this group at https://groups.google.com/group/limeware-foxray.
For more options, visit https://groups.google.com/d/optout.

[Duc M Do]

​Ricardo,

Thanks for the info. The site still uses ICC so no EVO anywhere.

Out of curiosity, I ran a query of the Modifications table looking for 'HISTORY' in the parameter field. To my surprise, it came up with nearly 28000 results (and that's only since early 2016). It appears that -- for the most recent occurrences, at least -- that .HISTORY.ENABLED is changed wholesale from ENABLED to DISABLED when we perform a LoadAll of compounds.

We'll explore filing a case with GCS as you suggested.

Thanks!

Duc

[Ricardo Abech]

Yes, I remember when we added this feature it wrongly added the HISTORY changes to all blocks for the first time. I believe this gets added when blocks are deleted or moved to a different CP. You can check.

You can probably safely delete them by running an advanced query:

DELETE FROM MODIFICATIONS WHERE PARAMETER like '.HISTORY.ENABLED' 

[Duc M Do]

Ricardo,

I'll do that delete to keep our database clean​. Thanks!

Duc