SystemLink Forum

cancel
Showing results for 
Search instead for 
Did you mean: 

Tag database breaks if tag path contains a newline character (SystemLink 2020 R2)

Solved!
Go to solution

Issue

I programmatically created SystemLink tags in LabVIEW and accidentally included a newline character in the tag path. This seemed to cause problems with the tag database:

  • The newline doesn't get replaced with an underscore, unlike spaces
  • I'm unable to update or delete the tag, even when logged in as administrator. (I can update/delete other tags with "good" names)

 

Here's what happens if a tag called "Hello\nWorld" is created:

 

bad-systemlink-tag.png

 

Suggestions

  • Newlines (and all other types of spaces that can be represented in a string) should be replaced by underscores.
  • "Build Path.vi" (or the upstream Salt service?) should sanitise the Minion ID. I had given my CompactRIO a shorter, nicer Minion ID by editing /etc/salt/minion_id. Out of habit, I added an empty line to the end of the file. This was what caused the initial problem.

 

Questions

So... how do I get rid of the unwanted tag? (Preferably without nuking my whole tag database)

Certified LabVIEW Developer
0 Kudos
Message 1 of 2
(1,413 Views)
Solution
Accepted by topic author JKSH

@JKSH wrote:

 

Questions

So... how do I get rid of the unwanted tag? (Preferably without nuking my whole tag database)


You should be able to use the LabVIEW API to delete the unwanted tag, or if you're familiar with HTTP APIs, you can access the tag HTTP API directly to delete the tag. The issue appears to be isolated to the web UI disabling the delete button when it shouldn't.

 


Suggestions
  • Newlines (and all other types of spaces that can be represented in a string) should be replaced by underscores.
  • "Build Path.vi" (or the upstream Salt service?) should sanitise the Minion ID. I had given my CompactRIO a shorter, nicer Minion ID by editing /etc/salt/minion_id. Out of habit, I added an empty line to the end of the file. This was what caused the initial problem.

Those are both good suggestions, thank you for reporting this.

Message 2 of 2
(1,373 Views)