Issue with SU_CompatMarkers Table when no Windows 10 systems are inventoried

[ngreeley]

I'm having a basic issue where I'm running the inventory script on Windows 11 machines, and as such, there are certain columns that aren't being created in the SU_CompatMarkers_CL table, which, when you go to populate the Power BI report, causes it to fail based on it's looking for specific fields, example: 21H2_BlockedFromUpgrade_s. Admittedly, I'm assuming that field is related to Windows 10, is it not?

NOTE: It also appears that I can't add those columns manually as they start with a number and Azure doesn't seem to like that.

[SMSAgentSoftware]

Hi, thanks for logging the issue. I've updated the Power BI template to display just Windows 11 23H2 in the readiness page since that's the current go-to OS version. Does that solve your issue?
https://github.com/SMSAgentSoftware/MEM/tree/main/Software%20Updates%20Reporting%20Solution/Power%20BI%20template

[ngreeley]

In case I end up having Windows 10, is it possible to do something around this part of the query, where, if it doesn't exist, returns null for the value?

W10_21H2_BlockedFromUpgrade=21H2_BlockedFromUpgrade_s,
W10_21H2_GatedBlockId=21H2_GatedBlockId_s,
W10_21H2_RedReason=21H2_RedReason_s,
W11_21H2_BlockedFromUpgrade=CO21H2_BlockedFromUpgrade_s,
W11_21H2_GatedBlockId=CO21H2_GatedBlockId_s,
W11_21H2_RedReason=CO21H2_RedReason_s,
W10_11_22H2_BlockedFromUpgrade=NI22H2_BlockedFromUpgrade_s,
W10_11_22H2_GatedBlockId=NI22H2_GatedBlockId_s,
W10_11_22H2_RedReason=NI22H2_RedReason_s

[SMSAgentSoftware]

Yes you could, for example, change the last line to:

W10_11_22H2_RedReason=column_ifexists(""NI22H2_RedReason_s"","""")

But it makes more sense to me to focus on the current W11 release.