...
Once connection is established, please review instructions here to get started with setting up an Assets import configuration. You can then access OnLink app from the “Manage your apps” menu to further configure and set the field level mapping.
OnLink allows you to pull data from either Classic or Pro API versions of JAMF.
Here’s an example mapping configuration when pulling in computer data. Any field available in this API can be used to map to the asset attributemobile device data from this classic API.
key:mobile_device.id=Device IDmap:mobile_device.serial_number=Serial Numbermap:mobile_device.device_name=Device Namemap:mobile_device.name=Namemap:mobile_device.model=Model
config:api=JSSResource/mobiledevices
Here’s a breakdown of some of the mapping configuration items:
Key or Map | Description |
|---|---|
| The keyword “key” refers to using ID as a unique identifier. This allows OnLink to update the record. |
| Maps device name to attribute |
| Can be set to any other API from JAMF as well. Update the mapping based on the API response to import data from any JAMF API to JSM Assets |
Any other field returned by the API can be used in the mapping. Similarly, you can use a Pro API to pull data as well. Here’s an example mapping configuration when pulling in computer inventory data from this pro API.
key:id=idmap:general.name=Namemap:general.platform=platformmap:groupMemberships=BAssets|Name=${groupMemberships}|arrayElement=GROUPIDconfig:api=api/v1/computers-inventory
OnLink processes data in two steps - Get Data and Import Data. To manually test, you can click on Get Data first and then wait until you see “No more pending records. Data will be imported on next Import run.” message in Job Logs. Then, click on Import. Production runs are fully automated based on the schedule you choose.
...