Can anyone provide inputs on how can we achieve sorting around firstname/lastname instead of userid.

Hi all,
We have a column in the db which stores userid.

We have a view that queries all other columns in addition to the userid.

While displaying the data on the grid, we are passing the userid to get the user's firstname and lastname.

Everything works fine, but when we sort on the this column, it sorts on the internal userid rather than the firstname/lastname that we had populated.

Can anyone provide inputs on how can we achieve sorting around firstname/lastname instead of userid.

Eg: Userid in db: "A123"

We are passing "A123" to a function to get its firstname/lastname which is "AAA 777".

Now, when we are sorting, it sorts on "A123" instead of "AAA 777".

One idea might be storing firstname/lastname in the db along with userid. If I use this approach, then I will have to modify my CDT to hold these values. I need to implement this change around several grids.

But, wanted to understand if there is any other way.

Any...

OriginalPostID-187277

  Discussion posts and replies are publicly visible

Parents
  • Hi Phani, just wanted to add one point to what sikhivahans mentioned. if you decided to go with the database approach, you can achieve the functionality without making any changes to your CDT. get your full name constructed in the query and alias the column with the same name; in this case you need not worry about the new CDT version and the existing CDT should work and minimal changes on your work. One additional advantage you get in this case will be to get the pagination as well through queryEntity rather than loading the entire data one time.
Reply
  • Hi Phani, just wanted to add one point to what sikhivahans mentioned. if you decided to go with the database approach, you can achieve the functionality without making any changes to your CDT. get your full name constructed in the query and alias the column with the same name; in this case you need not worry about the new CDT version and the existing CDT should work and minimal changes on your work. One additional advantage you get in this case will be to get the pagination as well through queryEntity rather than loading the entire data one time.
Children
No Data