Skip to main content
May 12, 2022
Solved

Sorting of Real time data in grid

  • May 12, 2022
  • 17 replies
  • 0 views

 i have performed  calculation of some status staying  in  grid  and that is changing on everyday basis i am not storing that value in any database .

and that status calculation is happening and dependent on many field . how can i apply sorting when dependency of that data is not on any particular field.

    Best answer by manishk0011

    Hi Himanshu,

    As venky said Implement the same logic at the view level, then the sorting will work as sorting will not work on logical values. You must be having all the data for a row at the view just modify the logic for status column .

    17 replies

    gopalk2865
    Participating Frequently
    May 12, 2022

    HI Himanshu, Are you getting any errors while applying sorting?

    May 12, 2022

    No Gopal error is not coming only thing is I am not able to sort data

    stefanhelzle0001
    Brainy
    May 12, 2022

    Did you try to make this a synched record and put this logic into a custom record field?

    May 12, 2022

    No Stefan 

    May 12, 2022

    Sort works only on fields not on logical value. My suggestion is create a custom field with this logic within your record and then you can use that field directly here and apply sort.

    docs.appian.com/.../custom-record-fields.html

    May 12, 2022

    can we create custom record field in view based record

    manishk0011
    May 13, 2022

    Hi Himanshu,

    As venky said Implement the same logic at the view level, then the sorting will work as sorting will not work on logical values. You must be having all the data for a row at the view just modify the logic for status column .

    davel001150
    May 12, 2022

    Does it need to still be based on a VIEW?  Have you fully considered just scrapping the view and creating it as an Appian synched record?  It honestly might sound like a lot of work, but might actually be less work than it sounds.

    I would, of course, if you go that route, create the custom synched record first, then delete the VIEW if you really determine you don't need it anymore after you develop it.  That's what we did, though granted on a very small project.

    peter.lewis
    Employee
    May 13, 2022

    Yeah I would be interested in understanding why you chose to use a view. If you're doing joins to reference data or calculations most of those can instead be achieved through record relationships and custom record fields respectively.

    May 13, 2022

    yeah like initially  we were not aware  that calculations would be come.