Enhancements to device and software contextualization workflows

Note:This enhancement is available with IT Visibility With Technology Intelligence Platform.

The following enhancements have been made to the Contextual Data Mashup:

•

Domain is now optional for device contextualization

Previously, when a hardware ID was unavailable, uploading device data using the Device Context Mashup required the Domain, Name, and Serial Number fields all to be populated, and would fail if Domain was blank or set to “Unknown”.

Now, you can upload device data even if the Domain field is blank or set to “Unknown”, as long as Name and Serial Number are provided. The system will match devices using Name and Serial Number when Domain is unavailable.

•

Blank or “Unknown” values now allowed for contextual attributes in CSV uploads

Previously, if any contextual attribute of type int, uint, bool, float, date, or datetime was blank or set to “Unknown” in a CSV upload, the contextualization process for that hardware or software would fail.

Now, CSVs containing one or more contextual attributes with blank or “Unknown” values are accepted. The contextualization proceeds using attributes with valid data, while attributes with blank or “Unknown” values are skipped.

•

Contextual attributes named “ID” are no longer allowed

Previously, if a contextual attribute named “ID” (case insensitive) was included in a CSV upload, the data would successfully upload into CDS, but the downstream data flow to PowerBI would break.

Now, users will not be able to create a contextual data source with an attribute named “ID”. This restriction is enforced at both the API and UI levels to ensure data integrity and prevent downstream issues.

These enhancements help streamline device data ingestion, reduce upload errors, and enforce best practices for schema design.

For more details about contextual data, see Contextual Data Mashup Overview in the Flexera One help.