Hi Everyone, We are seeing some strange behavior when we are populati

brettr

Certified Lead Developer

over 8 years ago

Hi Everyone,

We are seeing some strange behavior when we are populating a grid using a queryEntity inside of the with instead of a todatasubet. If we sort on a column that has all of the same data on the first page, and the same data on a couple rows on the second page, there are some rows that are never actually displayed on the grid. Our current theory is that this is occurring because there is no secondary sort field with a queryEntity, and the videos that I will link to later seem to support that. It looks like a query rule will have a secondary sort based on the "Sort query results by" configuration in the query rule itself if you change the pagingInfo.sortInfo that is passed into the query rule. Unfortunately, a queryEntity actually breaks if you pass it a pagingInfo that has an array of sortInfo, so I do not see a way to define, or force, a secondary sort field. According to documentation, it looks like sorting on multiple colum...

Discussion posts and replies are publicly visible

Parents

0 brettr
Certified Lead Developer
over 8 years ago

...ns is not supported on a queryEntity.

The below video shows a queryEntity retrieving data based on the pagingInfo saved in the grid (selecting 'Procurement Organization' to sort on). All of this is done inside a with():
screencast.com/.../hZ1e0My66IhV

The below video shows a query rule, with a default sort of 'Procurement Identifier', retrieving data based on the pagingInfo saved in the grid (selecting 'Procurement Organization' to sort on). All of this is done inside a with():
screencast.com/.../ZHI3dKXJEFUl

It looks like the query rule correctly displays all data without repeating while paging through it. We are not able to actually use a query rule in practice, because we require dynamic filters based on inputs. And unfortunately, we are not able to return all of the data to run it through a todatasubset because of the amount of data that would be returned. Has anyone run into this issue before with a queryEntity, and have you been able to resolve it...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 brettr
Certified Lead Developer
over 8 years ago

...ns is not supported on a queryEntity.

The below video shows a queryEntity retrieving data based on the pagingInfo saved in the grid (selecting 'Procurement Organization' to sort on). All of this is done inside a with():
screencast.com/.../hZ1e0My66IhV

The below video shows a query rule, with a default sort of 'Procurement Identifier', retrieving data based on the pagingInfo saved in the grid (selecting 'Procurement Organization' to sort on). All of this is done inside a with():
screencast.com/.../ZHI3dKXJEFUl

It looks like the query rule correctly displays all data without repeating while paging through it. We are not able to actually use a query rule in practice, because we require dynamic filters based on inputs. And unfortunately, we are not able to return all of the data to run it through a todatasubset because of the amount of data that would be returned. Has anyone run into this issue before with a queryEntity, and have you been able to resolve it...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data