CSV and XML Problems with various columns about 365inspect HOT 3 CLOSED

Looks good. Will test it out with the private version and report back the results.

~Leonardo

from 365inspect.

We believe the issue is a result of failing to define a delimiter character in the script. Delimiting on a comma character may result in unwanted behavior as some of the affected objects results return comma separated lists.
We will work on a better method of exporting to the various formats.

from 365inspect.

For now is the workaround to disable the following lines:

$result | Add-Member -MemberType NoteProperty -name Finding -Value $finding.Description -ErrorAction SilentlyContinue
$result | Add-Member -MemberType NoteProperty -name AffectedObjects -Value $("$($finding.AffectedObjects)" | Out-String).Trim() -ErrorAction SilentlyContinue
$result | Add-Member -MemberType NoteProperty -name Remediation -Value $finding.Remediation -ErrorAction SilentlyContinue
$result | Add-Member -MemberType NoteProperty -name References -Value $($refs | Out-String)  -ErrorAction SilentlyContinue

Those lines might have problems with the delimitation and or the objects exceeding more than 255 characters per column.

from 365inspect.