You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm importing tab separated data via Import-Excel and piping it to Export-Excel. The created Excel file is then imported to Sql Server via OpenRowset.
The problem is that the "empty" cells don't import in as NULL values, but rather as some sort of empty string.
If I open the same tab separated file with Excel and save as .xlsx it will import as NULL.
I guess it's technically not wrong for it to be "empty" strings. But kind of unexpected.
I have the same issue if I do "Invoke-Sqlcmd -OutputAs DataRows | Export-Excel" and try to import the thusly generated Excel
Any suggestion to on how to get around this?
The text was updated successfully, but these errors were encountered:
I'm importing tab separated data via Import-Excel and piping it to Export-Excel. The created Excel file is then imported to Sql Server via OpenRowset.
The problem is that the "empty" cells don't import in as NULL values, but rather as some sort of empty string.
If I open the same tab separated file with Excel and save as .xlsx it will import as NULL.
I guess it's technically not wrong for it to be "empty" strings. But kind of unexpected.
I have the same issue if I do "Invoke-Sqlcmd -OutputAs DataRows | Export-Excel" and try to import the thusly generated Excel
Any suggestion to on how to get around this?
The text was updated successfully, but these errors were encountered: