Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. 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.
Hi All,
I am trying to quey the view which has 20000 rows. when i apply filter to one of the calculated column which has 0 rows present, queryentity still throws below error.
Expression evaluation error at function a!queryEntity: An error occurred while retrieving the data. Details: Unexpected error executing query (type: [ELMRISKREDUCTIONLANDINGPAGEVWDT16641], query: [queryentity expression], order by: [[Sort[eucInventoryId asc]]], filters:[(currentReductionStage in TypedValue[it=103,v={Process Re-engineering/Non GFT/ITeSS,}])])
We tried optimizing the view as well, but no luck.
Any suggestion would be appreciated.
Discussion posts and replies are publicly visible
Views are notoriously known for performance issues. Any reason for not using synced records?
Ultimately the value of sync'ed records shine here - with an uncommon caveat about data stewardship.
If the view is in a remote data source that another team controls, then the Appian environment also (usually...) has access to the view's underlying tables and thus could sync / manage logic more directly. However, if that other team also controls the logic of the view, then suddenly that logic has to be synchronized across multiple technical teams. It turns into a people / governance problem at that point.