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.
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.
Discussion posts and replies are publicly visible
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.
Hello Shubham Aware ,
Sorry for the delayed response. The primary key is being generated in the view using the ROW_NUMBER() function. However, the view aggregates data based on the following three columns:
Column1 – Venky
Column2 – Appian
Column3 – Developer
Each row will have Venky_Appian_Developer like this for one column
Since the data is aggregated using this combination of columns, each aggregated record represents a unique combination of these values. Therefore, the resulting records will always be unique, which is why we configured this column as the unique identifier in the Record Type.But it is getting failed we haven't find the root cause for this ,Could you please help with this
drop ROW_NUMBER() and use the concatenated business combo (Venky_Appian_Developer) as the source key instead, or persist to a real table with a true identity PK. The combo is deterministic; ROW_NUMBER() is not