APNX-1-4205-040

RE: APNX-1-4205-040

Chris — Thu, 25 Apr 2024 18:25:08 GMT

Agreed, I might look at indexing on the view in this case as well.

Additionally, I would caution against querying based on a list of ID inputs, as this is not scalable if the list can grow continuously. Alternative solutions will depend on the use case and current configurations.

RE: APNX-1-4205-040

juergeng0002 — Thu, 25 Apr 2024 18:23:05 GMT

I bet, as mentioned in the error message, you are hitting the timeout or memory limit.

As Stefan mentioned, you have to find a different way to implement it.

What we did in a similar case:

We used a stored procedure to dump the content of the view every 15 minutes into a flat table (using a process model)

We defined a record type based on that table and inform the user on the UI at what time it was last updated.

Also, you have the capability to perform a sync on that flat table with data fabric by executing a 'fake deployment' of the record type
utilizing the Deployment APIs. Doing so, has the benefit that you don't have to deal with the primary keys.

Appian will sync the whole record type. Data Fabric is of course only an option, if the number of records (4 million) are not exceeded.

We have made good experience with this approach. Hope that helps.

RE: APNX-1-4205-040

Stefan Helzle — Thu, 25 Apr 2024 18:05:22 GMT

Well, I do not see a question.

But to solve this, you will have to speed up that view or find a different way to implement that requirement.