Keeping track of the empty values

Our applications replicate the complete data from the source to JSM Assets.

On the other hand, JSM Assets has a control mechanism for each import. For example, it checks the empty values for an import. Atlassian designs this control to prevent unexpected data removals. And it is configurable for each object type.

However, the default configuration of Assets imports ignores the empty values, unknown values, and missing objects outbound references. This configuration makes data replication partially possible.

An example of a possible scenario could be:

Application Name: Microsoft Intune Importer for JSM Assets

Issue Description: The Intune owner has not been removed. It still displays the previous owner in Assets.

Scenario: The Intune “Managed Device” has an owner. The owner leaves the company, and Intune reinstalls the device. Intune now doesn’t have the Primary User value.

Problem Description: The data is replicated without an error to Assets by the Pio importer application but is not updated because of the default import configuration of Assets.

Solution:

1- Login to JSM and open your Assets Object Schema.

2- Select “Schema Configuration”

3- Select the “Import” tab.

4- Expand the Intune import configuration by clicking “Edit mapping“ to see the object type mappings.

5- Click on the three dots and select “Edit object type mapping” for the Managed Devices.

6- Select “Remove” for the “Missing objects outbound references” parameter.

7- Select “Remove” for the “Empty values” parameter.

8- Select “Ignore” for unknown values.

7- Click save

Default configuration		Advised configuration for Pio Applications

Default configuration		Advised configuration for Pio Applications
Open		Open

 Related articles