After tinkering with CSV export / imports, adding or removing networkObjects is completely broken

[solakug]

Hi,

I wanted to try and add a few dozen network objects at a time and to do so, i first experimented with exporting my current configuration in a CSV file to see the exact format.

I then added the necessary fields to my liking, and proceeded to import the csv using veyon-cli networkobjects import However, once i had done this and i got an [OK] output, the list of network objects had not changed in Veyon Master. I checked in the Configurator panel, and sure enough no new entries were present, only the ones i had configured previously.

Out of curiosity, I tried a second export, and to my surprise the new objects were present, but i had also created duplicates of the initial objects.
So i tried deleting everything from the Configurator GUI, went back to do an export and .... nothing changed.
Every single object was still being exported to CSV as if nothing had changed in Configurator.
The field in the Configurator GUI was still blank though.

Then I opened Veyon Master again, and the objects field was littered with duplicate objects ( both computers and locations ). At that point, I opened up RevoUninstaller and completely uninstalled Veyon, and let Revo delete all registry entried and files associated with Veyon.
Rebooted my computer, re-installed Veyon, rebooted again.

Now, whatever i do, the configurator GUI will not work anymore, even after multiple full reinstalls / reboots.
I am able to add objects through veyon-cli networkobjects add but the GUI is completely useless.

Exporting a config file from another computer and importing it to mine does make objects appear in the GUI, but they are never added / seen in Veyon Master.

At this point, i don't want to use veyon-cli anymore, i'm fine with adding my 60+ or so objects individually from Veyon Configurator, but is there anything that can be done so that Configurator actually has an effect on objects ?

Thank you for your time

[tobydox]

I'm sorry for the problems you had with managing your network objects through the CLI. I guess veyon-cli didn't identify the location(s) properly in which to import the computers. It would be interesting to see the output of

veyon-cli config get BuiltinDirectory/NetworkObjects

before and after the import. May be you can reduce the import to a minimal case with just one entry?

Next I would also recommend to clear all objects before the import.