Skip to Main Content
AVEVA Product Feedback


Status Completed
Created by Guest
Created on Aug 19, 2022

Configurable default Attribute ConfigString

Right now, when you create an attribute in a template and assign it a Data Reference of PI Point, it defaults to a ConfigString of "\\%Server%\%Attribute%". %Server% has some known administrative headaches because what it populates as is dependent on the default server of the client tool.  But in our company we are constantly switching between environments and this causes mismatches. As recommended by OSI we have created an attribute in the root AF element called Server and gave it a string value of the name of our server.  Now when we create a new attribute we map a reference to that attribute instead of %Server%.  But if we forget to do that, then it goes back to %Server%.  We would like a way to configure (on a global basis) the default ConfigString for new template attributes.
  • ADMIN RESPONSE
    Aug 19, 2022
    AF 2018 SP2 allows you to designate a default PI Server per database and per PI System. This would greatly improve the process of moving AF databases from one machine to another.
  • Attach files
      Drop here to upload
    • Guest
      Reply
      |
      Aug 19, 2022
      If I can specify the archive that %server% points to as a property of the AF Server and/or Database then that will be great. One requirement that I would add is that this configuration setting has to be made available to be set programatically (my preference is through PowerShell). Right now when we delete our Test AF database and refresh it with a copy of Prod (all done in a PowerShell script) I need to be able to change the archive that the newly instituted database points to. Side requirement (not as important). Could it be setup with multiple servers? Like %Server% and %Server2%? Some of our AF Databases combine data from 2 different Data Archives and being able to set both with substitution parameters would be ideal.
    • Guest
      Reply
      |
      Aug 19, 2022
      Yes, it will be possible to change via AF SDK and Powershell. Regarding the side requirement, we will not likely implement the suggestion as it is possible for you to accomplish this by creating a root level element with attributes for these alternate servers. For example, creating a root element: "Servers" with attributes such as "Server1", "Server2", and then using a configuration string such as: "\\%@\Servers|Server2%\%Element%\%Attribute%