Some of the queryRecordTypes are working slow for us in prod. I am trying to monitor the performance and it has something 'performanceView.breadcrumb.recordQuery' highlighted. What does that mean and what part of the query/record it points to? Any idea
Also, Appian do recommend using queryRecordType to get the data from the related records too but when I have filters and logical expressions applied to them they are performing slow.
Discussion posts and replies are publicly visible
The problem with the records is that when you use user filters , and each one of them executes a rule when populated, the performance can be affected, because the filters are evaluated on each user interaction.
Remove some user filters and make a test please in order to identify is the problem is related with that point
Sorry by filters I meant query filters.
IN that case, check if the fields in the database that you use in the query filters are indexed.
As with user filters, try removing query Filters in order to find which one is causing the problem. Probaly that field won't be indexed
Is this whole setup using synced records? If yes, there is no need to try to optimize anything in the database.
Yes all the records are synced records. That's what I was wondering synced records are built to boost record performance and fast usage. But somehow they are slow for our users.
Well, what kind of queries are you doing? And how is the implementation? Using runtime custom record fields will probably not help. Filters with dynamic options will not help.
Some query filters involving basic operators like =, in and others in queries and logical expressions on the record fields and related record fields. Not using any custom record field or dynamics options.Does my records needs to be synced more frequently for this? I see all are synced but not necessarily every day some are only synced after the deployment.
The sync interval does absolutely nothing to query performance!
In such scenarios, I try to remove things step by step to identify the problematic one. Then I need to think about alternatives approaches.
And any idea about this yellow highlighted part
Sorry, never seen this before. But it says "performanceView", so I assume it is part of the internal implementation of the performance view itself. I would report that to Appian.