Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to filters rows from source in Object Type Mapping for Importing Assets

Yannick Mansuy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 22, 2026

I'm trying to update assets in Jira Assets with information from Intune via the Data Manager.

I'm able to pull data from Intune and set up an import, however the source data contains rows for multiple Object Types in Assets. I though creating individual mapping and filtering by AQL would work but I cannot get it update the assets if a filter is defined.

I've got 2 mappings which leverage "Asset Status" which is only present on existing Assets. I've tried using the column "OperatingSystem" = "Windows" from the source data but that did not work.

- Mobiles

AQL for mobiles: "Asset Status" IS NOT EMPTY AND objectType = "Mobiles"

- Laptops

AQL for mobiles: "Asset Status" IS NOT EMPTY AND objectType = "Laptops"

Any suggestions on how achieve this

2 answers

0 votes
Gideon Nolte _Eficode_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 27, 2026

Hi @Yannick Mansuy

AQL object filters for imports can be used to have one data source for multiple object types. So your initial hunch was right.

----
TL;DR
AQL Object Filters for Imports are applied on the change objects created during the import. Therefore the source data used for distinguishing the object's type needs to be imported. Furthermore, the object type should not be a part of the filter when trying to figure out the object type.

----

My mental model for these filters is as follows: The import configuration will draft all creations or updates for all mappings first. On this possible "draft" state, it will apply the filters. So filtering the values for an object type on said object type wouldn't really work and filtering on a column from the source data would not work as well.

Generally speaking, the filter should only include values that are imported. So your source column OperatingSystem should be mapped onto an attribute (e.g. "Operating System Family") - within the Laptop AQL object filter, you could then do "Operating System Family" = "Windows" or "Operating System Family" in ("iOS", "Android") for Mobiles maybe.

Step by step:

  • If it does not exist, create an attribute for "Operating System Family" for mobiles and laptops
  • In both mappings:
    • Map the OperatingSystem column form Data Manager to "Operating System Family" attribute in Assets
    • Map the Status column from Data Manager to the "Assets Status" attribute in Assets
  • Setup your AQL Object Filters as follows:
    • For Laptops: 
      • "Asset Status" IS NOT EMPTY AND "Operating System Family" = "Windows"
    • For Mobiles
      • "Asset Status" IS NOT EMPTY AND "Operating System Family" in ("iOS", "Android")

This way, the import config will "draft a state" in which each row from the source data will create a Laptop, as well as a Mobile, but it will filter out all Laptops, that do not have "Windows" as the "Operating System Family" and all Mobiles for which the "Operating System Family" is neither "iOS" or "Android". You can change the values for "Operating System Family" according to your case. 

Hope this helps.

Best Regards
Gideon from Eficode

0 votes
Fabian Lim
Community Champion
January 24, 2026

Hi @Yannick Mansuy

Welcome to the community!

Another options is to create two separate searches from Data Manager.  One for mobiles and one for laptops.  Then you would have two separate imports for each object to assets.

Regards,

Fabian

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events