Microsoft
@John B
It's a tab being appended after the comma. This appears to be a discrepancy between LP 2.2's interpretation of the CSV Output Format parameters data types and how PowerShell passes those parameters to LP 2.2. The LP 2.2 documentation suggests the following for the "tabs" parameter:
============
Tabs Parameter
============
Values: ON | OFF
Default: OFF
Description: Write a tab character after each comma separator.
Details: Setting this parameter to "ON" causes the CSV output format to write a tab character after each comma field separator, in order to improve readability of the CSV output.
However, from within PowerShell (via testing based on your question), a zero must be passed instead of "OFF". I will update LPS to account for this when generating scripts in the near future.
In the interim the workaround would be to change the tabs parameter to 0 instead of "OFF" in the script where the OutputParams are evaluated; the tabs parameter is approximately on line #66 in the script:
Change $OutputFormat.tabs="OFF" to $OutputFormat.tabs=0 and save the script.
After making the change the additional tab character should no longer appear in the output. As mentioned, I'll update the script template in LPS and update the download soon but try this as a workaround for now. Thanks for finding this.
