[SG-SCCM] Fix broken Last run datetime functionality/incremental processing for SG-SCCM Computer Identity - Known Error

[SG-SCCM] Fix broken Last run datetime functionality/incremental processing for SG-SCCM Computer Identity Description Last run datetime functionality/incremental processing broke for SG-SCCM Computer Identity.

Having "V_GS_WORKSTATION_STATUS.TimeStamp" as Last run datetime is breaking because of the dot walking not supported in some version of platforms JDBC.

Steps to Reproduce

1. Install SG-SCCM 3.7.0 2. Enable "Use last run datetime" feature. Note that the "Last run database field" value will be "V_GS_WORKSTATION_STATUS.TimeStamp". If necessary, clear the "Last run datetime" value. 3. After running SG-SCCM successfully, the "Last run datetime" field value will remain empty.

Workaround Customer can directly update his SQL statement to

SELECT name, domain, model, manufacturer, ResourceID, username, numberofprocessors, SystemRole, caption, Version, chassistype, LastHWScan, BIOSSerialNumber, SystemSerialNumber, UUIDSerialNumber, ChassisSerialNumber, BaseboardSerialNumber, TimeKey, OsTimeStamp, AssignedDate, OUName, AssetTag FROM ( SELECT v_GS_COMPUTER_SYSTEM.Name0 as name, v_GS_COMPUTER_SYSTEM.domain0 as domain, v_GS_COMPUTER_SYSTEM.Model0 as model, v_GS_COMPUTER_SYSTEM.Manufacturer0 as manufacturer, v_GS_COMPUTER_SYSTEM.ResourceID, v_GS_SYSTEM_CONSOLE_USAGE.TopConsoleUser0 as username, v_GS_COMPUTER_SYSTEM.NumberOfProcessors0 as numberofprocessors, v_GS_SYSTEM.SystemRole0 as SystemRole, v_GS_OPERATING_SYSTEM.Caption0 as caption, v_GS_OPERATING_SYSTEM.Version0 as Version, v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 as chassistype, CONVERT(datetime, SWITCHOFFSET(TODATETIMEOFFSET(V_GS_WORKSTATION_STATUS.LastHWScan,datepart(tz,SYSDATETIMEOFFSET())),0)) AS LastHWScan, v_GS_PC_BIOS.SerialNumber0 as BIOSSerialNumber, v_GS_COMPUTER_SYSTEM_PRODUCT.IdentifyingNumber0 as SystemSerialNumber, v_GS_COMPUTER_SYSTEM_PRODUCT.UUID0 as UUIDSerialNumber, v_GS_SYSTEM_ENCLOSURE.SerialNumber0 as ChassisSerialNumber, v_GS_BASEBOARD.SerialNumber0 as BaseboardSerialNumber, V_GS_WORKSTATION_STATUS.TimeStamp as TimeKey, v_GS_OPERATING_SYSTEM.TimeStamp as OsTimeStamp, v_R_System.Creation_Date0 as AssignedDate, null as OUName, v_GS_SYSTEM_ENCLOSURE.SMBIOSAssetTag0 as AssetTag FROM v_GS_COMPUTER_SYSTEM LEFT JOIN V_GS_WORKSTATION_STATUS ON v_GS_COMPUTER_SYSTEM.ResourceID = V_GS_WORKSTATION_STATUS.ResourceID LEFT JOIN v_GS_SYSTEM ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_SYSTEM.ResourceID LEFT JOIN v_GS_PC_BIOS ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_PC_BIOS.ResourceID LEFT JOIN v_GS_OPERATING_SYSTEM ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_OPERATING_SYSTEM.ResourceID LEFT JOIN v_GS_COMPUTER_SYSTEM_PRODUCT ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_COMPUTER_SYSTEM_PRODUCT.ResourceID LEFT JOIN v_GS_SYSTEM_ENCLOSURE ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_SYSTEM_ENCLOSURE.ResourceID LEFT JOIN v_GS_BASEBOARD ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_BASEBOARD.ResourceID LEFT JOIN v_GS_SYSTEM_CONSOLE_USAGE ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_SYSTEM_CONSOLE_USAGE.ResourceID LEFT JOIN v_R_System ON v_GS_COMPUTER_SYSTEM.ResourceID = v_R_System.ResourceID ) xx WHERE 1=1 Also, ask them to update "Last run database field" field to "TimeKey".

This should resolve the issue.