Getting StartIndex must not be greater than TotalCount issue

Certified Senior Developer

Hi All,

We are getting the following error as startindex cannot be greater than totalCount. Start index was 31 and totalcount was 0. We are using process report query for querying the data and for paginginfo, we are using fv!paginginfo. We are getting the above error only in prod and we are being notified via the error mail as part of the new appian release. No user has reported this issue. We are not able to understand why this error is occuring. One observation was when errors are triggered, startindex is having 11, 21,31,51 etc. Any suggestions will be helpful

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer

    hi    could you post your code snippet please that would be better idea

  • 0
    Certified Senior Developer
    in reply to Abhishek Karumuru

    a!queryProcessAnalytics(
      report: cons!REPORT_NAME,
      query: a!query(
        logicalExpression: a!queryLogicalExpression(
          operator: "AND",
          filters: {
            a!queryFilter(
              field: "c14",
              operator: "<>",
              value: loggedInUser(),
              applyWhen: ri!taskAssignement = cons!NAME[2]
            ),
            a!queryFilter(
              field: "c17",
              operator: "in",
              value: ri!PM_ID
            ),
          },
          logicalExpressions: {
            a!queryLogicalExpression(
              operator: "OR",
              filters: {
                a!queryFilter(
                  field: "c4",
                  operator: "=",
                  value: ri!search
                )
                
              },
              ignoreFiltersWithEmptyValues: true
            ),
            a!queryLogicalExpression(
              operator: "OR",
              filters: {
                a!queryFilter(
                  field: "c22",
                  operator: "=",
                  value: loggedInUser(),
                  applyWhen: ri!taskAssignement = cons!NAME[2]
                ),
                
              },
              ignoreFiltersWithEmptyValues: true()
            )
          },
          ignoreFiltersWithEmptyValues: true
        ),
        pagingInfo: ri!pagingInfo
      )
    )

    This is the query we are using in the read only grid. We are calling this query in the data parameter of the readonly grid and for ri!paging info, we are passing fv!paginginfo as the value.

Reply
  • 0
    Certified Senior Developer
    in reply to Abhishek Karumuru

    a!queryProcessAnalytics(
      report: cons!REPORT_NAME,
      query: a!query(
        logicalExpression: a!queryLogicalExpression(
          operator: "AND",
          filters: {
            a!queryFilter(
              field: "c14",
              operator: "<>",
              value: loggedInUser(),
              applyWhen: ri!taskAssignement = cons!NAME[2]
            ),
            a!queryFilter(
              field: "c17",
              operator: "in",
              value: ri!PM_ID
            ),
          },
          logicalExpressions: {
            a!queryLogicalExpression(
              operator: "OR",
              filters: {
                a!queryFilter(
                  field: "c4",
                  operator: "=",
                  value: ri!search
                )
                
              },
              ignoreFiltersWithEmptyValues: true
            ),
            a!queryLogicalExpression(
              operator: "OR",
              filters: {
                a!queryFilter(
                  field: "c22",
                  operator: "=",
                  value: loggedInUser(),
                  applyWhen: ri!taskAssignement = cons!NAME[2]
                ),
                
              },
              ignoreFiltersWithEmptyValues: true()
            )
          },
          ignoreFiltersWithEmptyValues: true
        ),
        pagingInfo: ri!pagingInfo
      )
    )

    This is the query we are using in the read only grid. We are calling this query in the data parameter of the readonly grid and for ri!paging info, we are passing fv!paginginfo as the value.

Children
No Data