-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQLScript Replacement \\n #33
Comments
Everything looks correct - check below code:
Output:
Note that new lines in value-part of json element has |
Thanks for the reply @NowinskiK The behaviour using config-prod.csv and without it, are different. |
George, can you show me the example of SQLScript (please scrub any client-related pieces). |
Yes of course, config-prod.csv contains this value (truncate for simplicity and obfuscation)
~Populate serverless - Datawarehouse database.json file: |
Could you show me also what the original file ( |
Sure, I've removed alot of the script (which contains environment specific storage names which is the reason for the replacement) but the same should apply no matter the length.
|
When trying to use config-prod.csv to replace the script in a sqlscript as part of a synapse deployment, I found that the library saves the file with escaped values, e.g. \n instead of \n etc. After debugging I found that it is due to the
$output = ($obj.Body | ConvertTo-Json -Compress:$true -Depth 100)
line in Save-SynapseObectAsFile.ps1.Test script:
Output:
The text was updated successfully, but these errors were encountered: