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

Asset Object Creation/Edit is not working when Filter Object AQL is used.

XMLWordPrintable

      Issue Summary

      When AQL in Filter Object is used like below,  AQL filters the objects that are being displayed correctly.

      ServerRole.objectId=756

      But While Creating New Object or Editing Existing object fails with below error

       

      {
          "errorMessages": [
              "No matching attribute for AQL clause (objectId = 756)"
          ],
          "errors": {}
      } 

       

      Steps to Reproduce

      Create 3 Objects types like below

      1. "Create Object" Object Type has attribute "Server" Reference to "Server" Object Type
      2. "Server" Object Type has attribute "ServerRole" reference to "Server - Role" Object Type.
      3. "Server - Role" Object Type is the 3rd  one which only has Name attribute.
      4. Now in "Create Object" for "Server" attribute add below Filter Object AQL
      ServerRole.objectId=756  
      1. Above will display only "Server" Objects that are referenced to "Server - Role" Object type with ID = 756.

      But while creating or saving the existing objects , it throws below error

       {
          "errorMessages": [
              "No matching attribute for AQL clause (objectId = 756)"
          ],
          "errors": {}
      } 

       

      Expected Results

      Object Should be Created or Edited as per the Filtered AQL Objects

      Actual Results

      Getting Error like : 

       {
          "errorMessages": [
              "No matching attribute for AQL clause (objectId = 756)"
          ],
          "errors": {}
      }

      Workaround

      Tweak the AQL like below which will work fine.

      object having outR(objectType = "Server-Rollen" and objectId in (756)) 

              188f29a851d8 Rahul Virahaniya
              e8ddb9406228 Arvind Kishore
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: