[BUG] Account names containing backslashes are not handled properly
See original GitHub issueFirst of all, I want to express my gratitude for this tool and extensive documentation. Nevertheless, I’ve just encountered a problem during the migration with some corrupted data for instance: a few Accounts are named with backslash - Edge\Communications GB
. Due to that I am receiving and the following error:
Error during execution of the command: line 1:735 token recognition error at: ''Edge\C'.
Is there any way to configure how the job should escape invalid characters like: backslashes, forward-slashes single quotes, duble quotes etc
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Why are backslashes and forward slashes not able to be used ...
By far the biggest culprit is database queries. Backslash is used as an escape character, slashes are used in regex, file paths, etc....
Read more >Bug: can not handle "/" correctly when reading registry item ...
Bug : can not handle "/" correctly when reading registry item #5536 ... Value names and data can include the backslash character.
Read more >Different behaviours of treating \ (backslash) in the url by ...
According to my experience when my ubuntu workstation is configured on domain with active directory, the user name created for me was according ......
Read more >Azure Data Factory (ADF) Escape Character Issue When ...
The problem this causes is when I have an empty string with just a backslash (or at the end of a string value),...
Read more >Zip files expand with backslashes on Linux, no subdirectories
One may experience the same problem with rar: Unrar creating files with backslashes in names instead of proper directory hierarchy.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello, @szymon-halik Do you use these invalid characters in the query string in the export.json or the issue is coming from the Tool during its internal operation ?
Could you provide your latest export.json + .log files to review ?
The case has been closed for the current moment. Feel free to reopen if your issue still persists.