Data and Records - Recent Threads

RE: Sync records for a record created from materialized view

Shubham Aware — Mon, 29 Jun 2026 17:30:25 GMT

Use a stable source key (UNIQUE_ID/UIN) as the record identifier - ROW_NUMBER() changes on every refresh, which is why sync fails. Appian only needs the key to be unique, non-null, and stable, not a real primary key.
Keep all rows in the source and add a status column to mark them processed instead of filtering them out.
Use record filters to hide processed rows. This stops records from disappearing, so sync never references missing Ids and avoids Delete Records, which can't run on a materialized view.
Enforce UIN uniqueness in the database or stored procedure, not in Appian sync logic.

Sync records for a record created from materialized view

dipaliawaghade — Mon, 29 Jun 2026 06:39:43 GMT

Issue with Dynamic Identifiers in Materialized View Causing Sync Failures

We are consuming data from an external view that only returns records where:

BPM_PROCESSING_STATUS IS NULL
BPM_CASEID IS NULL

This external view is built on top of a base table that contains all records.

Current Implementation

When a case is created in Appian, we update the base table using a Query Database Smart Service, populating:
- BPM_CASEID
- BPM_PROCESSING_STATUS (e.g., PENDINGFORAPPROVAL, REFERREDBACK, PROCESSED)
Since we do not have access to define a primary key on the source table/view (due to grant restrictions), we:
1. Created a Materialized View on top of the external view
2. Added a synthetic identifier column:
  
  SQL
  
  1
  
  ROW_NUMBER() OVER (ORDER BY UNIQUE_ID) AS ID
  
  Show more lines
3. Built an Appian Record Type using this materialized view (to leverage record filters, etc.)
4. Created a stored procedure to refresh the materialized view
5. Used:
  - Execute Stored Procedure Smart Service
  - Sync Records Smart Service

Problem

The identifier (ROW_NUMBER) is not stable.

Initially, suppose we have 3000345 records
When cases are created for some UINs, those records are updated in the base table
As a result, they no longer satisfy the condition (BPM_CASEID IS NULL, BPM_PROCESSING_STATUS IS NULL)
Hence, they disappear from the external view and the materialized view

Example:

Record count reduces from 3000345 → 3000335
Previously generated IDs such as:
- 3000271, 3000313, 3000341
After refresh:
- Some of these IDs (e.g., 3000341) no longer exist

Impact

The Record Type identifier changes dynamically
When we run Sync Records, Appian attempts to sync using old identifiers
Since those IDs no longer exist, sync fails

Attempted Workaround

Tried using Delete Record Smart Service
However, deletion is not allowed since the source is a materialized view

Key Concern

We need a way to:

Refresh the record data immediately
Ensure users do not create duplicate cases for the same UIN

Question

Is there a recommended approach in Appian to handle:

Dynamic datasets where records disappear after updates
Unstable identifiers (ROW_NUMBER-based)
Immediate refresh/sync of record data
Preventing duplicate case creation for the same UIN

Comparison for two rows of same record data

pavang5769 — Wed, 06 Aug 2025 09:09:33 GMT

We have a requirement for comparison of same record type data and get the difference of the data & columns. We are aware of "CDT Diff Utilities" which does the same operation and gives the expected output. However we are looking for similar way of plugin availability or workaround to achieve the desired functionality.

Note: We are not looking for manual comparison of the record fields and the data, as we need to perform the comparison across all record types in the application and it will be become very tedious process to achieve by manual comparison.

RE: Comparison for two rows of same record data

venkatesanr1106 — Thu, 25 Jun 2026 09:26:04 GMT

thanks Jesse for the reply, however this option a! Keys says that the passed parameter of wrong type even though i used the a!fromJson ,I tried multiple way this did not work for me , I manually writing each and doing the comparison and do history update , Direct table changes work well with a!keys whereas when we use JSON this option seems to be erroring out.

RE: Sync Record Type returning inconsistent data

Shubham Aware — Mon, 22 Jun 2026 16:45:34 GMT

Most likely the record sync cache was stale or temporarily inconsistent, so queryRecordType() returned null even though the database value existed.
Since a manual sync fixed it, the root cause is usually a sync-layer mismatch, not the CDT or table structure.

Sync Record Type returning inconsistent data

sugithrag — Mon, 22 Jun 2026 14:49:35 GMT

Hi, while querying data using query record type in one specific field (which is an integer type, mostly the values will be 1, 2 or 3) is returning null even the value is present in the database. While using query entity value is returning and in record data preview value is displaying but in the query record type alone it is returning null one time and returning value on clicking test value again. It's a sync record type and there is no sync failure, and no changes were made in database table structure and in CDT. By syncing the record manually this issue is resolved but I want to understand the root cause.

Thanks.

RE: Sync Record Type returning inconsistent data

Stefan Helzle — Mon, 22 Jun 2026 16:36:51 GMT

Can you share the code of your record query?

RE: Comparison for two rows of same record data

Jesse Knight — Mon, 22 Jun 2026 12:28:01 GMT

If I'm understanding your issue correctly, a!fromJson() would convert the text to a map, which would allow usage of a!keys(). If it's invalid json, this will not work.

RE: Comparison for two rows of same record data

venkatesanr1106 — Mon, 22 Jun 2026 12:19:25 GMT

is there any way we can compare JSON and load the data in history like this ? , please advise

i tried to convert json and pass in whereas keys are not allowing this and says this as Text

RE: Security for fields in record table

Ali Sabry Ashroff — Thu, 18 Jun 2026 23:57:38 GMT

Thank you. Was using 'Users found in' groups and no records were visible until logged off and logged back

Security for fields in record table

skzahed_09 — Thu, 26 Jun 2025 06:45:30 GMT

So i have 3 fields in a record table namely A,B,C and also 3 groups namely A,B,C. So my doubt here is, is it possible to set security to the fields separately.

For example if i place a user in group A, then i should see only the A field and the other B and C fields should not be visible to me.

If it is possible, can anyone guide me how i can achieve it.

Selectable in Read Only grid

srinivaast629400 — Wed, 10 Jun 2026 11:48:00 GMT

Hi,

I have a grid fiield which is selectable. I am showing the filtered data in the grid. When the data is filtered the id will vary with row numbers like if id 2 and 5 is shown in first 2 rows it won't match with actual row number and the row is not getting highlighted after selection but the values are getting saved. The row is getting highlighted only when the row number matches the identifier. I have just used foreach loop and added extra parameter row number and mapped with fv!index. I have used this in identifier. The row is getting highlighted now but when there is a large number of data I am facing performance issue due to foreach loop. Is there any alternate way to achieve this ?[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:634d0c95-5f7a-4aa0-9345-30fc5f7163e1:type=text&text=%20a%21forEach%28%0D%0A%20%20%20%20items%3A%20local%21data%2C%0D%0A%20%20%20%20expression%3A%20a%21map%28%0D%0A%20%20%20%20%20%20uin%3A%20fv%21item.uin%2C%0D%0A%20%20%20%20%20%20uinDescription%3A%20fv%21item.uindescription%2C%0D%0A%20%20%20%20%20%20totalAmount%3A%20fv%21item.totalAmount%2C%0D%0A%20%20%20%20%20%20rowCount%3A%20fv%21item.rowCount%2C%0D%0A%20%20%20%20%20%20rowNumber%3A%20fv%21index%0D%0A%20%20%20%20%29%0D%0A%20%20%29%0D%0A%20%2F%2A%20Grid%20field%20code%2A%2F%0D%0A%20%20a%21gridField_25r2%28%0D%0A%20%20%20%20%20%20%20%20%20%20label%3A%20%22Exception%20By%20UIN%22%2C%0D%0A%20%20%20%20%20%20%20%20%20%20data%3A%20local%21expUin%2C%0D%0A%20%20%20%20%20%20%20%20%20%20selectionValue%3A%20ri%21selectedId%2C%0D%0A%20%20%20%20%20%20%20%20%20%20selectionSaveInto%3A%7B%0D%0A%20%20%20%20%20%20%20%20%20%20a%21save%28%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20ri%21selectedId%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20append%28%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20ri%21selectedId%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20fv%21selectedRows.rowNumber%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%29%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%29%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20a%21save%28%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20local%21deselectedId%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20index%28fv%21deselectedRows%2C%20%22rowNumber%22%2C%20%7B%7D%29%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%29%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20if%28%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20rule%21AHE_notBlankorEmpty%28local%21deselectedId%29%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20a%21save%28%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20ri%21selectedId%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20difference%28ri%21selectedId%2C%20local%21deselectedId%29%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%29%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%7B%7D%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%29%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%7D%0D%0A%20%20%0D%0A%20%20]

RE: Selectable in Read Only grid

Harsha Sharma — Wed, 17 Jun 2026 06:13:23 GMT

To elaborate on this the Row number can vary depending on filtered data and thus should not be relied for selection saves. Instead a data row's unique identifier (primary key) doesn't change. So save the unique identifier instead of row number in selection variable.

RE: Selectable in Read Only grid

EREN_YEAGER — Tue, 16 Jun 2026 09:14:06 GMT

You do not need to inject a rowNumber via a loop. You can achieve this seamlessly by using your data's actual primary key (like uin) as the grid's identifier.

example here

RE: applyWhen queryLogicalExpression not working

sugithrag — Mon, 15 Jun 2026 13:41:05 GMT

Sure, Thanks Shubham

applyWhen queryLogicalExpression not working

sugithrag — Mon, 15 Jun 2026 10:09:54 GMT

Hi, Im facing an issue in queryLogicalExpression where 'AND' operator is used and there are 3 query filters in it with applyWhen parameter is passed which is evaluated as false in all the 3 filters but still this expression got executed instead of ignoring it. Is the applyWhen parameter will work only for separate queryFilter and not for the filters added in logical expression? Could someone help me to understand the behaviour?

Thanks

RE: applyWhen queryLogicalExpression not working

Shubham Aware — Mon, 15 Jun 2026 13:37:05 GMT

applyWhen exists only on a!queryFilter(), not on a!queryLogicalExpression().
It drops just that one filter - it never skips a whole logical-expression block. When all leaf filters drop, the empty nested expressions still get processed, so your top-level block isn't ignored.

Build the blocks conditionally - if(<cond>, a!queryLogicalExpression(...), null) and a!flatten() the list so nulls fall out.

RE: applyWhen queryLogicalExpression not working

EREN_YEAGER — Mon, 15 Jun 2026 12:31:10 GMT

To make the yellow expression block disappear entirely when those conditions are met, you need to lift the applyWhen logic up to the parent layer. Instead of calling this parameter inside the individual a!queryFilter blocks, you must apply it directly to the top-level a!queryLogicalExpression that you want skipped.

Note : if you want an entire logical block (like the one highlighted in yellow) to be ignored based on a condition, the applyWhen must live on that specific block. Relying on inner filters to turn false will only clear out those specific inner filters, leaving the outer OR structure active and running.

RE: applyWhen queryLogicalExpression not working

sugithrag — Mon, 15 Jun 2026 11:03:20 GMT

Sure, it's a nested expression where in all the queryLogicalExpression highlighted in the box contain applyWhen parameter and it is false so I've expected the top level queryLogicalExpression (highlighted in yellow) should be skipped

RE: applyWhen queryLogicalExpression not working

EREN_YEAGER — Mon, 15 Jun 2026 10:51:27 GMT

Yes, applyWhen absolutely works inside a!queryLogicalExpression().

The reason your query is still running instead of being ignored is : When all filters inside a logical expression evaluate to false, Appian empties the list entirely. In Appian, an empty filter list doesn’t mean "ignore this query" or "return nothing", it means "return everything." The system treats it as a blank canvas with no restrictions, which is why your query still executes and fetches data.

could u give us more clarity on how and where you are applying the applywhen parameter. a code snippet would be helpful.

RE: applyWhen queryLogicalExpression not working

mikes519171 — Mon, 15 Jun 2026 10:32:00 GMT

The Are You a Charlotte? Podcast 2026 Kristin Davis Leopard Print Sweater gives off a stylish yet relaxed vibe. I appreciate clothing pieces that make a statement without requiring a lot of accessories, and this sweater seems to do exactly that while remaining comfortable for regular wear.

RE: Sync Failed On Records

Shubham Aware — Mon, 15 Jun 2026 08:07:38 GMT

Sync validates uniqueness on one source key field only, so it must be a single, unique, non-null column.
Check if you have any null column.

Sync Failed On Records

Goddati Venkatesh — Mon, 15 Jun 2026 05:23:54 GMT

Hello everyone,

In the recent update (version 26.1), we received a feature that allows us to create sync-enabled record types using a view as the data source.

In our case, we have a view where we aggregate three fields (e.g., Name, Type, and ID). Since these fields are aggregated, each row is unique, and we have configured this combination as a unique key in the record type.

Whenever a user updates information in the related tables, the view reflects the latest data. However, since we are using sync-enabled records, the updated data is not immediately available in the record.

To handle this, we added a Sync Smart Service at the end of the process. But whenever a new record is created or updated with Name, Type, and ID, the smart service fails with the below error.

Since the aggregation ensures there are no duplicate values for this column, and even in the view we see only a single row for each combination, I need guidance on how to handle or resolve this error.

Expression evaluation error at function a!queryRecordType Cannot apply operator [INCLUDES] to field [englishconentnew] in a!queryFilter(). The valid data types for [INCLUDES] are [ Integer, (Decimal), Boolean, Date, Date and Time, Recieved Extra Long Text

iswaryan3520 — Wed, 10 Jun 2026 11:09:13 GMT

I need to filter data in a record type but the field I want to apply filter on is extra long text it's throwing error . My actual requirement is I have to show the data in grid with serach options. In the grid data 800 rows are there so I am trying to use custom filters since I cannot use searchbox becase I am not using record data as data source that's because if the grid column need to display exra long text content it should inly use the query record type . so basically I am facing issue with extra long text but i need it because my data have characteres more than 9000 to 12000 . They all bascially html templates .Is there any way I can have option to filter the data not exact data but matches the query .

RE: Expression evaluation error at function a!queryRecordType Cannot apply operator [INCLUDES] to field [englishconentnew] in a!queryFilter(). The valid data types for [INCLUDES] are [ Integer, (Decimal), Boolean, Date, Date and Time, Recieved Extra Long T

Harsha Sharma — Wed, 10 Jun 2026 14:14:44 GMT

In that case, AFAIK there is no way to filter on an extra long text column.