Visual Studio installs gets inferred to Visual Studio 2022 due to missing suite componentsDescriptionIn discovery maps, Visual studio suite components were deactivated by content team, so that only Visual Studio software models with edition 2022 have suite components. This caused issue for suite engine to infer all visual studio installs to use Visual Studio 2022 suite, since it is the only edition that has suite components. This directly leads to wrong "inferred_suite" column for visual studio installs that are not 2022 (for example Visual studio 2019 Professional Windows). This also leads to wrong "minimum viable software model" selection, and incorrect license usage. This can be fixed by applying the update set from CSTASK820246. This will prevent a install to set inferred suite to the suite product that is the same as the installed product. For example, Visual studio 2019 install will not set inferred suite to Visual studio 2022. Steps to Reproduce 1. Create software model for Visual Studio 2022 Professional with suite components2. Create software model for Visual Studio 2019 Professional with no suite components3. Create software install of Visual Studio 2019 Professional4. Run reconciliation and wait for it to complete5. Observe in the cmdb_sam_sw_install table that the install for Visual Studio 2019 Professional has inferred suite of Visual Studio 2022 ProfessionalWorkaroundApply the update set from CSTASK820246 or PRB1765646Related Problem: PRB1765646