Unable to fetch data using query entity

RE: Unable to fetch data using query entity

Mike Schmitt — Mon, 20 Jan 2020 11:00:19 GMT

Correct.

RE: Unable to fetch data using query entity

Ashwin — Mon, 20 Jan 2020 05:36:33 GMT

So as per my understanding you are suggesting that we have to use includes function to get the expected result by adding a column in DB which would be of type text and a replica of the package id which is int

RE: Unable to fetch data using query entity

Mike Schmitt — Fri, 17 Jan 2020 12:47:01 GMT

[quote userid="36948" url="~/discussions/f/rules/18176/unable-to-fetch-data-using-query-entity/71499"]its not necessary to use INCLUDES although if i use IN it is not fetching the package id starting with 1 or 2 or 3 or anothing[/quote]

The use case you're describing does require INCLUDES, though. That's what I was explaining in my prior answer. IN does something completely different -- it would never give you the result you're currently thinking of, as it finds exact matches within an array of query inputs.

RE: Unable to fetch data using query entity

Ashwin — Fri, 17 Jan 2020 05:55:11 GMT

yes it is integer type and i am trying to find all the package ID starting with 1 but nor IN neither INCLUDES are working to fetch the result

eg:- if i have a data with 123,124,125,126 and if i try to find with 1 then it should result all the list of array

RE: Unable to fetch data using query entity

Ashwin — Fri, 17 Jan 2020 05:53:41 GMT

its not necessary to use INCLUDES although if i use IN it is not fetching the package id starting with 1 or 2 or 3 or anothing

code below

if(
rule!TMOS_isEmpty(
ri!packageID
),
{},
index(
a!queryEntity(
entity: cons!TMOS_ETY_WF_EXEC_AUDIT,
query: a!query(
filter: a!queryFilter(
field: "packageID",
operator: "IN",
value: ri!packageID
),
pagingInfo: a!pagingInfo(
startIndex: 1,
batchSize: - 1
)

packageID(array type-integer)

RE: Unable to fetch data using query entity

Mike Schmitt — Thu, 16 Jan 2020 13:48:22 GMT

The "INCLUDES" operator is intended for comparing text, so it wouldn't be expected to work on integer data (which I assume your "packageID" is). "IN" should work, but is used for exact matches against an array, i.e. you'd query "IN" and pass in an array i.e. {11, 22, 33}, and any packages with an ID of 11, 22, or 33 (but not "7225") would be returned.

Assuming I'm correct about packageID's type, and if you really need to do an "INCLUDES" search against it from an interface, for example, then you should be able to create a View that is basically a recreation of that table but with the addition of an additional column (i.e. "packageIdText") where you typecast the original packageID to text. If you get that working, and create a query entity against that view instead of the table you were originally querying, you should be able to do an "INCLUDES" query on the new text-type column.

RE: Unable to fetch data using query entity

Stewart Burchell — Thu, 16 Jan 2020 13:25:57 GMT

This is basically saying that Appian can't compare two different types of data. What datatype is the field 'packageID'? (ri!packageID appears to be 'List of Number (Integer)'