-
Notifications
You must be signed in to change notification settings - Fork 518
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
M365DSCReport: Add support for creating a report in CSV-format #5501
Conversation
$newRow = $modelRow.Clone() | ||
if ($row -gt 0) | ||
{ | ||
write-verbose "add separator-line in CSV-file between resources" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
write-verbose "add separator-line in CSV-file between resources" | |
Write-Verbose -Message "Add separator-line in CSV-file between resources" |
$newRow.Value = $value | ||
} | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this empty line.
begin | ||
{ | ||
if ($PSBoundParameters.ContainsKey('Delimiter')) | ||
{ | ||
$Delimiter = $PSBoundParameters.Delimiter | ||
} | ||
} | ||
process # required with DynamicParam | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indentation is not correct, leading to a curly bracket on the same line as another end block on line 778.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Pull Request (PR) description
This PR adds support for -Type CSV in New-M365DSCReportFromConfiguration and adds dynamic parameter -Delimiter when -Type CSV is used
This Pull Request (PR) fixes the following issues
I'm having issues creating an Excel-report of a configuration. On my local PC where I'm not a local admin the generation of the report fails with a CIM-error and on my admin-server I don't have Excel available. The obvious solution (for me) is to create the report in CSV-format and import it into Excel later.
Task list
Entry should say what was changed and how that affects users (if applicable), and
reference the issue being resolved (if applicable).