I have an issue with a a!queryEntity where the local!datasubset.totalCount is co

johng373 over 8 years ago

I have an issue with a a!queryEntity where the local!datasubset.totalCount is correct in the query rule, but is wrong in the interface which calls this query rule. I am trying to display this data in a grid. I think this has to do with paging and found some other posts about this issue but the fixes mentioned do not seem to work for me so I must be missing something fundamental.
Basically what is happening is I can see that 101 records are being returned in the a!queryEntity through local!datasubset.totalCount but when I display this data in a grid, only 68 records are displayed. Within my grid, the "totalCount" parameter is set to local!datasubset.totalCount.
My pagingInfo is set to the same amount in both the a!queryEntity and the rule which displays the data. Also, if I change the batch size to -1 on both the query entity and the rule, I get all expected results, however, I do not want to display all 101 records at once. I wa...

sampleCode.txt

Discussion posts and replies are publicly visible

0 johng373 over 8 years ago

...nt to display 20 at a time.

Here is a sample of my code. I removed a bunch of filters and fields on the rule for simplicity's sake.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 monikar over 8 years ago

Hi John,

Can you please try the attached sample code. And I've made the following changes to the code:

1. Made pagingInfo as rule input to the query entity rule as you want to get 20 records at a time
2. Using the same local variable local!pagingInfo while querying the data used rule!getRequest which is used to save the value of GridField.
Sample code - Modified.txt
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 johng373 over 8 years ago

thanks for your response. I made the change you recommended, however, the same symptom occurs.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 8 years ago

It could be that some of the filters are causing the result to be different from what you expect.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tim
Certified Lead Developer
over 8 years ago

I would have a closer look at your source data as it sounds like you have duplicate values in your identifier field. Try running your query with a batchSize of -1 and then a batchSize of 0 and see if the totalCount values are different.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 johng373 over 8 years ago

Yes, that is correct about the duplicate values but that's exactly what I want to return. If I change the batchsize to -1 I get back 101 records. If I change it to 0 I get 68 records. The 68 records are the distinct serial numbers associated with each of my request. Each serial number can have 1 to many of the same ids.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 johng373 over 8 years ago

Found the fix for this issue. My underlying CDT had the wrong field defined as the PK which was causing incorrect totalCount numbers. The underlying CDT points to a DB View so I neglected to identify exactly which field shall be unique. I feel pretty silly now but thanks for helping me talk through it. :)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel