Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-14801

When multiple values exist in the import source, the object type attribute reference AQL becomes case sensitive in Assets imports

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • Assets - Import
    • None

      Issue Summary

      Jira Service Management Assets imports allow users to create references to other objects when configuring import mappings. AQL by default should be case-insensitive as noted in the AQL documentation, however it was found that when multiple values are being set from the data source during the import, the search becomes case-sensitive and fails to create the references when there is a case mismatch.

      Steps to Reproduce

      In this example I will use two Schemas to demonstrate the behavior.

      Setup schema one

      1. Create a new schema called Service Station
      2. Click on the schema configuration and ensure the option Allow others to select objects from this schema is checked
      3. Create an object type and call it Location
      4. Create the following object type attributes:
        1. Name: City Type: Default Type Value: Text
        2. Name: State Type: Default Type Value: Text
        3. Name: Location ID Type: Default Type Value: Text
      5. Create two objects with the following values:
        1. Object one (example key STATION-123:
          1. City: Austin
          2. State: TX
          3. Location ID: austintx
        2. Object two (example key STATION-124:
          1. City: Denver
          2. State: CO
          3. Location ID: denverco

      Setup schema two

      1. Create a new schema called Vehicle
      2. Create a new object type and call it Car
      3. Create the following object type attributes:
        1. Name: Color Type: Default Type Value: Text
        2. Name: Service Location Type: Object Type Value: Location (This will be the object type created in the previous steps on the other schema)
      4. Create one object with the following values:
        1. Name: BMW
        2. Color: Red
        3. Service Location can be left empty

      Create import file

      Configure the following CSV file called importsource.csv:

      Name,Color,ServiceLocation
      BMW, Blue,Denverco||austintx

      Note: The D in Denver is upper case, which is a mismatch from the value set on the referenced object.

      Setup import

      1. Click Schema configuration on the Vehicle schema
      2. Navigate to the Import tab
      3. Click Create import
      4. Select CSV
      5. Set any name for the import and select importsource.csv as the file, toggle the Automatically create object types and attributes mapping to off
      6. Create the import
      7. Expand the Edit mapping and click Create mapping
      8. Select the Car object type and leave settings as default
      9. Create the mapping for the data source fields to their destination attribute:
        1. Name (Identifier) => Name
        2. Color => Color
        3. ServiceLocation => Service Location
      10. On the Service Location mapping, set the following in the AQL section:
      "Location ID" LIKE (${ServiceLocation${0}})

      Once configured, enable the import and run it.

      Expected Results

      Both SERVICE-123 and SERVICE-124 are linked to the object as referenced.

      Actual Results

      Only STATION-123 is linked because there is a mismatch between the source and object attribute case.

      Workaround

      When importing multiple values that will reference existing data in Assets, ensure that the case sensitivity matches between the source data and the destination data.

              Unassigned Unassigned
              f189ef36d400 Andras M.
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: