How to identify source values with Assets imports
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When working with Assets integration imports, it sometimes becomes necessary to identify which values are being sourced from the external tool.
This KB guides you in pinpointing which values are originating from the source and the attribute used in Assets. While we will use the Assets Azure integration as our example, the principles can be applied to any type of import.
Environment
Assets
Solution
Suppose we've configured the Assets Azure integration to gather detailed data from Microsoft Azure. During the import synchronization process, we noticed that some object attributes of type Date are not being populated from Azure.
For the purpose of this example, we'll focus on five attributes from the Managed Device Object Type.
Steps for troubleshooting
- For the Object Type that we want to troubleshoot, create a new attribute named 'test' of type TEXT. You can use any other name if you prefer.
- In the Import configuration, expand the Object Type mapping and create a new map. Select all the previously mentioned attributes as the "Data Locator". For the "Assets Attribute", select "test", which is the new attribute we created in the first step.
The aim of this process is to identify how the data from Azure appears. If there's an issue with date formatting, this method allows us to see exactly how the date data from Azure is fetched.
- Sync the import
- After you've completed these steps, navigate to the Objects and examine the "test" attribute. You will be able to see how the date is being transferred from Azure.