I will be able to make mass edits to large number of tags using the Find and Replace tool without having to manually make any changes using the tag browser which can be slow and painful. Once the file opens, I will see all of my tags arranged in a large JSON object, having my tags laid out in front of me in a text editor will give me flexibility.
#Mp3tag export tags plus
I will right click on the JSON file and select to open it using notepad plus plus, you can of course use a text editor of your choice. I have both of the files here on my file explorer. This way, if there is any type of collision conflict it just skips it and moves on without the error message. Now if you did not want the error message to appear, we can close it, try our import once more and set the collision policy to ignore.
This error is telling me Hey, the tags you're importing already exists, I will abort the import. With Abort you will get an error message at the end like so. Basically, when we are importing tags, how should admission handle any sort of path collisions that exist during an import. Now, you'll want to be aware of the collision policy in the right hand side here. The Legacy CSV format in older versions of ignition does not include alarm configurations in the export file. You will note that down below under files of type the CSV is supported. A window will open prompting us to select the tag export file we wish to import. And you will be asked if you want to import tags to the root. You will see a warning explaining to you that no folder or UDT definition was selected. So I will simply click on the kebab drop down menu and select Import tags. If I do not select a location at all and choose to import tags, all my tags will be imported into the location in my tag browser. So it is important to be cautious when importing tags. If I select my query tags folder and go through the import process using one of my tag exports we took a few seconds ago, I will have essentially imported my entire tag provider into the query tags folder which may not be ideal. Always be mindful of where you import your tags. So you wanted to import some of your tag exports, you first need to select whatever location you want your tags to be imported into, in your tag browser. I can then press Save to save my tags in my desired location in XML format. Or alternatively, you can simply right click and select Export tags and simply change our files extension from JSON to XML like so. If you want it to export your tags as XML, we can select our tags once more, head to the tag explorer button. I will then get a small pop up telling me that my save succeeded. I will leave the default JSON file option and press the Save button to save my export to my desired location. You will get a little save window where you will be prompted to select your file save location, we support two types of tag exports, XML and JSON. I'll click on the kebab drop down list here and select Export tags. In my case, I want to export my entire tag provider so I will select all my tags like so. Tag exports and imports are facilitated from the tag browser and your designer, you simply need to select the tag or tag folders you want to export. A tag import can be performed while the gateway is running without the need for any downtime.
However, gateway restores require the gateway service to be stopped temporarily. You can always take a gateway backup which will backup your entire gateway, including your tags. So you want to make some large scale changes to a particular tag provider, it might be a good idea to backup your tags. In some cases, you may need to backup your tags. In this lesson, we will talk about Tag imports and exports.
0 kommentar(er)
