Currently, the Applications SQL statement for the SCCM integration fetches data according to the following logic:

SELECT [ResourceID], [TimeStamp], [DisplayName0], [InstallDate0], [Publisher0], [Version0] FROM [v_GS_ADD_REMOVE_PROGRAMS_64]
 
SELECT [ResourceID], [TimeStamp], [DisplayName0], [InstallDate0], [Publisher0], [Version0] FROM [v_GS_ADD_REMOVE_PROGRAMS]
 
SELECT [ResourceID] ,[TimeStamp], [NormalizedName] AS [DisplayName0], [InstallDate0], [NormalizedPublisher] AS [Publisher0], [NormalizedVersion] AS [Version0], [InstalledLocation0] FROM [v_GS_INSTALLED_SOFTWARE_CATEGORIZED]

Views v_GS_ADD_REMOVE_PROGRAMS and v_GS_ADD_REMOVE_PROGRAMS_64 contain information about software registered in the Add/Remove programs list on Windows, whereas view v_GS_INSTALLED_SOFTWARE_CATEGORIZED lists information from different tables to provide additional data about the installed software.

This can result in duplicate values after an SCCM import is done using the Assets SCCM integration due to small differences in application name or version.

The suggestion is to improve the logic in order to normalize and deduplicate values from those different views in order to ensure unique values after import.