Hi
Think I found a critical bug.
We are doing some testing with command based import/export and the csv sync.
Running ASG-RD 2015 Patch 6.
If ASG is unable to open the source file for a csv sync it seems to handle the sync as if the source file to compare with was empty.
In other words if you set it to delete objects that do not exist it will actually wipe the entire connections tree.
The ideal approach in these situations would be for ASG-RD to cancel the entire sync when unable to find/open/read the source file.
In the current situation we have had this bug happening in 2 different situations. When the csv file was opened in Excel or when the file had a different process lock preventing it to be read/written.
Think I found a critical bug.
We are doing some testing with command based import/export and the csv sync.
Running ASG-RD 2015 Patch 6.
If ASG is unable to open the source file for a csv sync it seems to handle the sync as if the source file to compare with was empty.
In other words if you set it to delete objects that do not exist it will actually wipe the entire connections tree.
The ideal approach in these situations would be for ASG-RD to cancel the entire sync when unable to find/open/read the source file.
In the current situation we have had this bug happening in 2 different situations. When the csv file was opened in Excel or when the file had a different process lock preventing it to be read/written.