Connect 2 schema's

[Bernhard Bergman]

I want to connect to schema's based through an email adress-key.

The first schema holds the Azure AD accounts.

The second schema has all the imported Intune devices.

How to connect these 2?

[Arkadiusz Wroblewski]

Hello @Bernhard Bergman 

Yes, you can reference objects from one Assets schema in another. Enable "Allow others to select objects from this schema" on the Azure AD schema, then add an Object attribute on the Intune device object type pointing to the Azure AD account object type.

That said, if you want the import to resolve that reference automatically from the email address that part isn't possible yet. Atlassian still has that limitation for external imports across schemas. The workaround is to import the email as plain text first, then set the actual object reference afterwards through automation or the REST API.

cross-schema reference = yes
cross-schema external import mapping by email = not directly currently.

[JSDCLOUD-11024] Ability to reference object types in other schemas using External imports - Create and track feature requests for Atlassian products.

Allow other schemas to reference objects from a schema | Assets | Atlassian Support

[Bernhard Bergman]

I have this AQL, but I want to make the emailadress as the search variabele in my automation Rule.

objectTypeId = 29 AND "Owner Email Address" IN (“b.bergman@maars.nl”)

I’m looking for objects which have the right emailaddress in a different schema.

[Arkadiusz Wroblewski]

Hello @Bernhard Bergman

Yes, that part should work with automation.

If the email is coming from another field, just replace that smart value with the one from your rule.

Then automation can search the object in the other schema by email and use the returned object afterwards. Lookup objects gives you {{lookupObjects}}, and Branch on AQL gives you {{object}}.

The only limitation is the one from my earlier reply: cross-schema references are supported, but external imports still cannot directly create that cross-schema reference during import.

One small thing: if {{reporter.emailAddress}} returns empty, that can also be caused by profile visibility. In that case, use the field or form value where the email is actually stored in your rule.