Insight External Import: How to reference an object type in another schema?

[Lori Guymon]

I am trying to setup the schema and mapping for an import using this documentation: https://developer.atlassian.com/cloud/insight/imports/schema-and-mapping/ 

Using the example in this document to create and schema and object mapping, what would I change in this portion of the sample code if the referenced object type ("Operating System" in this case) is NOT in the same object schema as the the Hard Drive object type?  So Hard Drive is in schema "Disk Analysis Tool" schema and Operating System is in "Infrastructure" schema

Any help would be appreciated.

[Andrea · Accepted solution]

Hi @Lori Guymon

Currently it's not possible to reference an object type in another schema when setting a object reference attribute value using external imports.

I've raised a suggestion for this that you can vote and watch for updates: https://jira.atlassian.com/browse/JSDCLOUD-11024

If you don't mind sharing, it would be great to understand:

1. What is the source of the data you're importing? (e.g. a spreadsheet, local database, 3rd party SaaS tool?)
2. Why are the object types split across different schemas currently?

This will help us to understand the use case a bit better to decide the best way to solve this.

Thanks!

[Lori Guymon]

See below...

[Lori Guymon]

Thanks for the reply Andrea.  I thought this was the case but wanted to confirm.  

I am trying to create a continuous nightly (non-manual) update of our Asset data into Insight from our current asset system as well as updating our People object type in Insight from our HR system.  (Both types of data are stored in other databases).  Our Asset data contains an Assignment attribute that needs to reference the People object type. The people data will always be read only but eventually our Asset data will be updateable.  We were thinking we needed to split these object types into 2 different object schemas to provide 2 types of security (assets - updateable, people read only).   We just don't want folks who can update assets monkeying around with the people data.  :-)

For now it sounds like we do not have an alternative but to these two object types in the same object schema if we want to load the Assignment attribute with a people object type reference.  We do not go live until next year so maybe this will become a feature before our go live date.

Our external import is coming together pretty good with the exception of the referencing objects from another schema AND I found out that I cannot set the User type reference in the import either.  It sounds like that is a feature that is coming soon too...I hope. 

[Andrea]

We just don't want folks who can update assets monkeying around with the people data.  :-)

😆 I appreciate that. You can also restrict access via roles at the Object Type level https://support.atlassian.com/jira-service-management-cloud/docs/remove-users-or-groups-from-an-object-type-role/ but depending on the number of object types you'll have that might not be a sustainable option.

Thanks for sharing :) Glad the external imports have been helpful. The User type reference and this issue are both on our radar.