The Flexera Business Adapter is a critical component used to integrate data from various sources into the Flexera IT asset management system. The adapter may not function correctly in certain scenarios if the Location ID field is not populated with the appropriate data.

When the Location ID field on another data mapping is left blank or does not link back to the Location_out ID, the Flexera Business Adapter may exhibit the following symptoms:

• Data separation failures: The adapter may fail to separate corporate locations from parents, so your results show, for example, United Kindom/England/Cheshire as one location, rather than three locations of United Kingdom, England, Chesire, all being a child of the former. 
• Inaccurate records: Assets or devices may be associated with the wrong corporate location, leading to inaccurate tracking of hardware and software assets.
• Errors: Business adapter may fail to match on location and fails to update records. 

The Flexera Business Adapter requires the Location ID field to be populated correctly because it uses this information to establish the relationship between assets and their respective locations. If this field is missing or contains inaccurate data, the adapter cannot map assets correctly within the IT asset management system.

Solution

To resolve Flexera Business Adapter failures due to an empty or incorrect Location ID field, follow these steps:

1. Check the configuration of the Object ID on the Location data mapping. 

As shown in the image below, this is not an option that can be selected from the drop-down menu. It should be automatically populated from the object ID value of the data location node.

If anyone has manually typed "Location_ID” or “LocationOut_ID”, it’s best to remove the location node and then add the location back into the adapter.

2. In the Data Transformation field, ensure it’s set to split the location into different children upon a value such as a slash (/) or some other character. 

This ensures that your locations, whether matched or newly created, are organized so that each location after the slash is created as a child of the last. 

For example:

Your source data may look like the image below.

Setting the Split values on field as the slash (/) character ensures that the corporate locations are split up the example below.