search

ThomasKur / M365Documentation

Automatic Microsoft 365 Documentation to simplify the life of admins and consultants.
Other
300 stars 45 forks source link

Issue to writing Word export file #14

Closed BDOMichaelKirstNeshva closed 1 year ago

BDOMichaelKirstNeshva commented 2 years ago

HI,

I try now for hours to run your report and export that as Word Dok. But it isn't running. I'm using your older Intune-Conditional Access report, that is running without any errors...

I found a discussion at https://github.com/xceedsoftware/DocX/issues/226 and ask me, is this the right version for an "modern powershell" program? Because, many MS CSP / MSP working with Windows clients.. like W10 or W11. And when I reading at that forum, that new .net versions are only supportet in commercial versions, how do you support newer .net windows clients? i am not a developer and if i have misunderstood something, then i apologize.

here is my comandline:

`PS C:\WINDOWS\system32> import-module azuread PS C:\WINDOWS\system32> import-module pswriteword PS C:\WINDOWS\system32> import-module BDO-M365Documentation PS C:\WINDOWS\system32> Connect-M365Doc -ClientId '6bab04xxxxxxxxxxxxxxxxx8c1cce' -ClientSecret (ConvertTo-SecureString 'F5Yq8Rpeq7xXaeaCJdaoxxxxxxxxxxxxxxx' -AsPlainText -Force) -TenantId '97a6baca-xxxxxxxxxxxxxxxxx-31'

PS C:\WINDOWS\system32> $doc = Get-M365Doc -Components Intune -ExcludeSections "MobileAppDetailed" Invoke-DocGraph : Der Remoteserver hat einen Fehler zurückgegeben: (404) Nicht gefunden. In C:\Program Files\WindowsPowerShell\Modules\xxxxxxxxocumentation\Internal\Collector\Intune\Get-MdmAppleConfiguration.ps1:21 Zeichen:23 + ... c.Objects = Invoke-DocGraph -Path "/deviceManagement/applePushNotific ... + ~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-DocGraph

PS C:\WINDOWS\system32> $doc | Write-M365DocWord -FullDocumentationPath "C:\Users\Micxxxxxxxxshva\xxxxxxxxxx\M365-Dok\$($doc.CreationDate.ToString("yyyyMMddHHmm"))-xxxxxxxxxxx-M365-Doc.docx" WARNUNG: Get-WordDocument - Document: C:\Users\Micxxxxxxxxshva\xxxxxxxxxx\M365-Dok\$($doc.CreationDate.ToString("yyyyMMddHHmm"))-xxxxxxxxxxx-M365-Doc.docx Error: Der Typ [Xceed.Words.NET.DocX] wurde nicht gefunden.
Der Typ [Xceed.Document.NET.Container] wurde nicht gefunden. In C:\Program Files\WindowsPowerShell\Modules\pswriteword\1.1.12\PSWriteWord.psm1:1036 Zeichen:114 + ... mPipeline, Mandatory = $false)][Xceed.Document.NET.Container]$WordDoc ... + ~~~~~~ + CategoryInfo : InvalidOperation: (Xceed.Document.NET.Container:TypeName) [], RuntimeException + FullyQualifiedErrorId : TypeNotFound

Der Typ [Xceed.Document.NET.Container] wurde nicht gefunden. In C:\Program Files\WindowsPowerShell\Modules\pswriteword\1.1.12\PSWriteWord.psm1:1036 Zeichen:114 + ... mPipeline, Mandatory = $false)][Xceed.Document.NET.Container]$WordDoc ... + ~~~~~~ + CategoryInfo : InvalidOperation: (Xceed.Document.NET.Container:TypeName) [], RuntimeException + FullyQualifiedErrorId : TypeNotFound `

regards Michael

ThomasKur commented 2 years ago

Thanks for your feedback. The xceed docx library is one of the biggest word libraries, but yes, the open source version is always a few version behind the commercial one and lacks some features. Using an installed word is another option but then it depends on the version of word which is installed and I know some people which are running the script in Azure Automation. Therefore the library is currently not a bad thing but yes it does not support everything. Or do you have better ideas?