Datastype subset is coming as object,object instead of real data values when passed in process model

RE: Datastype subset is coming as object,object instead of real data values when passed in process model

David Jimenez — Wed, 28 May 2025 07:03:12 GMT

a!localVariables(

  /*You store the dataset in this variable*/
  local!query: a!queryEntity_22r2(
  entity: cons!ABC_ENTITY_USERS,
  query: a!query(
    pagingInfo: a!pagingInfo(
      startIndex: 1,
      batchSize: 1,
      sort: a!sortInfo(field: "updatedDateTime")
    ),
    selection: a!querySelection(
      columns: {
        a!queryColumn(field: "caseId"),
        a!queryColumn(field: "caseStatus"),
        a!queryColumn(field: "folderId")
      }
    ),
    logicalExpression: a!queryLogicalExpression(
      operator: "AND",
      filters: {
        a!queryFilter(
          field: "caseId",
          operator: "=",
          value: ri!clientCases.caseId,
          applyWhen: not(
            rule!APN_isBlank(ri!clientCases.caseId)
          )
        ),
        a!queryFilter(
          field: "caseStatus",
          operator: "not in",
          value: {"STARTED"},

        ),
        a!queryFilter(
          field: "docsSent",
          operator: "is null"
        )
      }
    )
  )
),
/*Index the variable and store the result in a new variable or just return the dataset*/
/*local!dataset: index(local!query, "data", null)*/
index(local!query, "data", null)

)

RE: Datastype subset is coming as object,object instead of real data values when passed in process model

varung120549 — Wed, 28 May 2025 05:31:35 GMT

Hi Dusty ,

You can simply index by storing the above query in a local variable or directly using index() function.

a!localVariables(
  local!data:a!queryEntity_22r2(
  entity: cons!ABC_ENTITY_USERS,
  query: a!query(
    pagingInfo: a!pagingInfo(
      startIndex: 1,
      batchSize: 1,
      sort: a!sortInfo(field: "updatedDateTime")
    ),
    selection: a!querySelection(
      columns: {
        a!queryColumn(field: "caseId"),
        a!queryColumn(field: "caseStatus"),
        a!queryColumn(field: "folderId")
      }
    ),
    logicalExpression: a!queryLogicalExpression(
      operator: "AND",
      filters: {
        a!queryFilter(
          field: "caseId",
          operator: "=",
          value: ri!clientCases.caseId,
          applyWhen: not(
            rule!APN_isBlank(ri!clientCases.caseId)
          )
        ),
        a!queryFilter(
          field: "caseStatus",
          operator: "not in",
          value: {"STARTED"},

        ),
        a!queryFilter(
          field: "docsSent",
          operator: "is null"
        )
      }
    )
  )
),
index(local!data,"data",{})
)

RE: Datastype subset is coming as object,object instead of real data values when passed in process model

Dusty — Wed, 28 May 2025 04:49:46 GMT

David Jimenez when you say indexing the object, could you please show with an example what it means or how I can index in my query below:

a!queryEntity_22r2(
entity: cons!ABC_ENTITY_USERS,
query: a!query(
pagingInfo: a!pagingInfo(
startIndex: 1,
batchSize: 1,
sort: a!sortInfo(field: "updatedDateTime")
),
selection: a!querySelection(
columns: {
a!queryColumn(field: "caseId"),
a!queryColumn(field: "caseStatus"),
a!queryColumn(field: "folderId")
}
),
logicalExpression: a!queryLogicalExpression(
operator: "AND",
filters: {
a!queryFilter(
field: "caseId",
operator: "=",
value: ri!clientCases.caseId,
applyWhen: not(
rule!APN_isBlank(ri!clientCases.caseId)
)
),
a!queryFilter(
field: "caseStatus",
operator: "not in",
value: {"STARTED"},

),
a!queryFilter(
field: "docsSent",
operator: "is null"
)
}
)
)
)

RE: Datastype subset is coming as object,object instead of real data values when passed in process model

David Jimenez — Tue, 27 May 2025 21:21:26 GMT

Not necessary, maybe is just the way that appian shows the information inside your process. That's why I asked if you are able to access the data.

RE: Datastype subset is coming as object,object instead of real data values when passed in process model

Dusty — Tue, 27 May 2025 20:27:51 GMT

Thank you for the response David Jimenez

yeah but I want to get the whole datasubset value and indexing would kill that right? For example, in my script task output I'm just calling rule!getuserdata(user: pv!userdetails) and saving this to a pv of type datasubset.

RE: Datastype subset is coming as object,object instead of real data values when passed in process model

David Jimenez — Tue, 27 May 2025 20:18:47 GMT

Have you tried indexing the object to see if you can work with the data?