Import of CSV stopped working correctly?

[thogud]

Hi

We are using ASG-RD 2015 fully patched.
For at least the 2 last patches we have been seeing strange behavior with missing ConnectionDestination for newly imported connections (CMDB sync were we auto import new components every 10 minutes into ASG-RD).

And they get the ConnectionDestination when we do a full daily sync later on.
Could it be the import have stopped working?

We import command based.
Command:
"C:\Program Files (x86)\ASG-Remote Desktop 2015\ASGRD.exe" /instance:"ASG_RDP" /loginintegrated:true /loginsubmit /importaction:ConnectionsCsv /importsource:\\10.116.186.8\e$\ftproot\ASG\Eksport\ASG_export_regularly.csv /importoutput:\\10.116.186.8\e$\ftproot\ASG\Logg\asg_import_log.txt /importid:4ac05db6-ae3c-481e-a4d7-08a4f18a5a92

Attached an example i tested with now.
This ends up like this:



And unless I am blind I cannot see any issue with the import format. It looks identical to the stuff we export from ASG-RD and the column name is correct for the destination.

[DevOma]

Ok I imported on my machine and there is also no destination - I will check asap and come back to you

[thogud]

Thanks again

[DevOma]

Seems to be the connection protocol

Please set a valid value for protocol (RDP, SSH, ...) or remove this column from your csv file - then sync/import will work again!

[thogud]

Hi again

Has this been changed then?

Cause previously empty protocol defaulted RDP.
Ref:
http://forum.visionapp.com/showthread.php?tid=8942

We don't have the protocol for every new object instantly, often that comes with later discovery when the OS is known. So earlier blank set it to RDP automatically in ASG-RD, and a future sync would change to SSH when Linux was dicovered and written in the ConnectionProtocol field for the daily sync.

Worst case I will write the CMDB export code to set RDP if the value is blank on the export.
But this was not like this on previous patches of ASG-RD 2015.

It supported blank fields in the import then. Often you will have different connection types having different fields filled, so sounds strange if the ConnectionProtocol field should behave in a special way and be required a value if it exists?

But yeah, ConnectionDestination is filled when I also include a value for the ConnectionProtocol (or remove it).
Removing ConnectionProtocol in the import defaults RDP as the protocol, but leaving it as a blank value mess up another value (ConnectionDestination).

Is this really intentional on development level?
Find it a bit odd, but please explain if it should be this way

[DevOma]

You are right - the change was with the thread you mentioned - I will fix it, so if there is no sync (that was the issue in the other thread) it will have an default - will be fixed in the next version

[thogud]

Sounds good Import and sync can default RDP if blank in the csv and it is a new connection or ConnectionProtocol is already has empty values in ConnectionProtocol in ASG-RD (should not be possible).

But if you import or sync and it match an already existing connection. And that has lets say SSH as the ConnectionProtocol, and the csv you import or sync contains a blank ConnectionProtocol it should leave it as SSH and not trigger the default RDP setting for blanks.

That way both will work (the fix in the forum thread I linked + importing new connections with a blank ConnectionProtocol field)

[DevOma]

Yes - and it's fixed already :-)

[thogud]

Yes - and it's fixed already :-)

Perfect :D Thanks again and have a nice day/weekend