PI Vision Manual Data Entry AF

Hi,

 

i have found this Topic:

https://pisquare.osisoft.com/s/Blog-Detail/a8r1I000000HbIkQAK/pi-vision-manual-data-entry

 

Is it possible to set AF Attribtes?

 

I always get the following errors:

https://msr-srv-vision/piwebapi/attributes?path=%5C%5CMSR-SRV-AF%5CNHM-Energie%5CSandm%C3%BChlen%7CStart%20Datum

->

{

"Errors": [

"The specified path was not found. If more details are needed, please contact your PI Web API administrator for help in enabling debug mode."

]

}

 

The Path are a AF Database path.

 

 

 

  • Hi,

     

    i have Changed any User Secutitys.

     

    But now i have this Error Message:

    1. 2: {Status: 405, Headers: {Content-Type: "application/json; charset=utf-8", Allow: "GET,PUT"},…}
      1. Content: {Message: "The requested resource does not support http method 'POST'."}
      2. Headers: {Content-Type: "application/json; charset=utf-8", Allow: "GET,PUT"}
      3. Status: 405

     

  • I'm in the same boat as you. Just started this week trying to do this. I was able to use the testing code at https://github.com/AVEVA/sample-pi_web_api-common_actions-python to confirm I my API is set up correctly and works. This let me build a database, element template, element, point, and do both read/write, then erase it all; and it worked great. Then when attempting to use this same test code to write a value to an existing AF tag in my normal AF database I get this same 405 Method Not Allowed {"Message":"The requested resource does not support http method 'POST'."} error you're getting. Hopefully, one of us will figure out the issue or someone will lead us to the next step in our troubleshooting adventures. Maybe you'll have some luck with the sample code I linked to find the problem, I know if I find an answer I will definitely post it here as well.

  • I for one have been really disappointed with AVEVA's progress in PI Vision. At the most recent user conference, they had a demo of things they added over the last two years, and it was basically a new authentication option. To me, the symbols should be constantly evolving and we should be getting more refined settings, such as defining our own event frame url or be able customizing it.

     

    The lack of new features has caused us to look else ware for the features we need in PI Vision. We found a vendor that adds allot of features that should be included in PI Vision. I would check this company out, they have been great to work with and offer very affordable solutions. https://www.software-athlete.com/

  • Due to the numerous different ways customers want "Manual Data Entry" to be done in PI Vision, I doubt that AVEVA will implement the feature. Granted, imo, it can be done in a way that will satisfy 95% of customers. I just don't see it being addressed, or at least not for quite some time.

     

    For the time being, the best option is to use custom symbols that meet your specific needs. I know it's not the best or desired approach for many companies due to supportability though.

  • Hi ​, sorry for the late reply, but this is possible using custom symbols like Manual Data Entry+. You can learn more about it here: PI Vision Custom Symbols Library

  • Hi,

    Yes, it is possible to set AF Attributes, but the error you are seeing usually indicates that PI Web API cannot resolve the AF path you’re providing. A few things to check:

    • Make sure the AF path syntax matches exactly what PI Web API expects (including escaped characters, correct database name, and element hierarchy).
    • Confirm that PI Web API is configured to expose the AF database you are targeting. If the database is not registered or access permissions are missing, you will get a “path not found” error.
    • Verify that the account running PI Vision (often the app pool identity) has read/write access to the AF server and database.

    If your main goal is to allow operators to update AF Attributes directly from PI Vision, the recommended approach is to use a Manual Data Entry symbol. This custom symbol integrates with PI Web API to send values back to PI Points or AF Attributes, bypassing the need for users to interact with raw PI Web API requests. It provides a user-friendly interface where operators can enter or adjust values (e.g., start dates, setpoints, weights, moisture percentages), and those inputs are automatically pushed to the underlying AF Attributes or PI Points.

    You can find more about this solution here: Manual Data Entry Symbol – BizOps Consulting.

    In short:

    • PI Web API can write to AF Attributes, but you need the correct path and permissions.
    • The Manual Data Entry symbol simplifies the process, providing a reliable and intuitive way for end-users to input values directly in PI Vision.