Problems with TrendClient object appearing in Aveva OMI.

Hello Jakob,

You might be experiencing issues with using the .NET controls within OMI as in earlier versions of the offer this wasn't a supported feature (2017).. there is a workaround to this as indicated below.

https://softwaresupportsp.aveva.com/#/knowledgebase/details/000021465?lang=en_us

There should also be a "HistoricalTrendClient" control as part of the Galaxy that can be utilized however the .NET Controls be found at the following directory, if you'd like to experiment with the documented steps above.

C:\Program Files (x86)\ArchestrA\Framework\Bin\AVEVA_Software__LLC__aaHistClientTrendControl.dll

Hi Edward, thank you so much for your help. 

One thing that keeps confusing me about the OMI,  when looking for support material and answers related to product support (which is like navigating through a jungle on the support page) , AVEVA OMI vs Intouch keeps being mixed a lot,  are they not two different types of OMI solutions?   

The article you refer to is related to Intouch. does it also apply to AVEVA OMI?   There are many cases where Intouch and OMI is mentioned either seperately or at the same time, which is confusing,  for instance, Intouch Access Anywhere seems to be the name of the solution being we use to view Aveva OMI viewapps through a web browser,  access level control in viewapp, seems to be a property called intouch access level etc.  

Is there anyone that can point me to some reading material about the difference?

Hello Jakob, 

The article provided applies to OMI, I've taken note of the discrepancies and will consult internally regarding clarifications to documentation and product support. We do have materials that available regarding product name changes that might be helpful but don't go into the detail that you may require. 

https://www.aveva.com/content/dam/aveva/documents/info/product-naming/AVEVA_Product_Naming_Transition_Guidebook_21-12.pdf

Hello Jakob, 

The article provided applies to OMI, I've taken note of the discrepancies and will consult internally regarding clarifications to documentation and product support. We do have materials that available regarding product name changes that might be helpful but don't go into the detail that you may require. 

https://www.aveva.com/content/dam/aveva/documents/info/product-naming/AVEVA_Product_Naming_Transition_Guidebook_21-12.pdf

Thank you again, really appreciate this forum and being able to get support like this!

Thank you for your positive feedback, Jakob! We appreciate your participation and great questions.