Manual Event Data Entry

Hi Arbind​,​

The request goes to your PI Web API Server. I wonder if your PIVision server name is an alias. Also, it doesn't seem to accept any requests other than Get and Put methods. To change this behavior, you'll need to adjust the piwebapi server setting, stored in PI AF Server>Configuration database. Consider adding an alias to your CORSorigins and adding POST to corsMethods.

Refer to: https://docs.aveva.com/bundle/pi-web-api/page/1023022.html

Hey Jinmo, even after completing all the configuration for the piwebapi server, I am still stuck with a new error related to the format. Can you help me to overcome with this issue

Hey, I wanted to inform you that I have successfully resolved this error. Could you please assist me with it?

Hi Arbind​,

Please recheck your request URL (resource) for your Batch.body.1.

Here you are using datastream.Path to get the attribute path.

Can you print out the result of var getDataStreamUrl(dataStream.Path)?

This should be in the accepted format for Path Syntax for your attributes.

Hey Jinmo, Its really a great help from your side, like I have resolved issues at every step. But with a few basic things, I am really stuck. This is really new and challenging task for me Please do help me to overcome the issue I am having related to the URL part, i.e., updateOption=replace' is not a valid URI, path=undefined piwebapi/attributes?path=undefined:, "Content": "The resource 'F1RS8QjbgsDbYk6_ESqRYc3z0QU0VSMDAx?updateOption=replace' is not a valid URI." Can you help me find out the correct URL or assist me with code changes? It will be like a great thank-you to you.

Arbind​ ,

The shared picomm.txt file doesn't seem to be the same version as the one you shared above.

Judging from the WebID, this is the webID of PISystem, F1 'RS', which is AF Server. There is no ?updateOption in this controller as far as I can see.

You should try with a test Attribute first on body >> 1.<Resource>.

Plus, if you know the path already, you can also simply build the WebID directly according to the WebID2.0 specification. This step will remove need for the step 1.

Arbind​ ,

The shared picomm.txt file doesn't seem to be the same version as the one you shared above.

Judging from the WebID, this is the webID of PISystem, F1 'RS', which is AF Server. There is no ?updateOption in this controller as far as I can see.

You should try with a test Attribute first on body >> 1.<Resource>.

Plus, if you know the path already, you can also simply build the WebID directly according to the WebID2.0 specification. This step will remove need for the step 1.