Invoke-DatabaseQuery issue

[darkwizard90]

Line |
115 | Invoke-DatabaseQuery -Database $Database -Sql $sql -NonQuery
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Exception calling "ExecuteNonQuery" with "0" argument(s): "Binder Error: Could not find key "userprincipalname" in struct Candidate Entries: "uniqueName""

[merill]

@darkwizard90 can you attach a zip of the logs folder found inside zt-export folder? tx

[darkwizard90]

@merill i tried twice in different location and in both cases the logs folder is empty

[DnS94]

Disclaimer: Generated by Claude AI.

I ran into this same issue on ZeroTrustAssessment 2.2.6 with Microsoft.Graph.Authentication 2.36.0 and PowerShell 7.5.5.

I was able to work around it with a single change in Export-Database.ps1 inside the Get-RoleSelectSql function (line 61):

# Before
cast(r.principal.userPrincipalName as varchar) as userPrincipalName,
# After
cast(r.principal.uniqueName as varchar) as userPrincipalName,

After this change (and restarting PowerShell to clear the cached module) the assessment completed successfully. It looks like the Microsoft Graph API has changed the property name from userPrincipalName to uniqueName in the role assignment/eligibility data.

[darkwizard90]

Disclaimer: Generated by Claude AI.

I ran into this same issue on ZeroTrustAssessment 2.2.6 with Microsoft.Graph.Authentication 2.36.0 and PowerShell 7.5.5.

I was able to work around it with a single change in Export-Database.ps1 inside the Get-RoleSelectSql function (line 61):

Before

cast(r.principal.userPrincipalName as varchar) as userPrincipalName,

After

cast(r.principal.uniqueName as varchar) as userPrincipalName,
After this change (and restarting PowerShell to clear the cached module) the assessment completed successfully. It looks like the Microsoft Graph API has changed the property name from userPrincipalName to uniqueName in the role assignment/eligibility data.

it fixed the issue. thanks

[merill]

This has been fixed in the preview version of the module. Please test and re-open if this is still an issue. Thanks!