Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
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.
Discussion posts and replies are publicly visible
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.
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.
yeah like initially we were not aware that calculations would be come.
Peter this Custom record field does not support now () function is there any substitute for now() function in custom record field.
This will not work as the calculation of the value for the custom record field is not made at query time, but at the time of writing the data.
Ah okay, unfortunately it isn't possible to use now() in a custom record field yet, although stay tuned for releases later this year! We're definitely working on this and hope to allow for query-time calculations like this soon :)