HI,
In my Appian app I have a datatype (item) which has item_id column as primary key and this column is marked in Appian to generate next unique identifier. At the same time user can add new entry using form and then process model use write to data store entity node.
Mentioned solution worked fine.item_id was generated by Appian until I have added multiple rows to DB using SQL. After that Appian throw an error as it generates next identified based on Appian previous identifier.
How to force Appian to refresh sequence on Appian side so we can use form to add new entries using write to data store entity?
Details: org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update: java.sql.BatchUpdateException: ORA-00001: unique constraint (APN_WARSAW_RAD.SYS_C0030000) violated
Discussion posts and replies are publicly visible
Hi Furman,
Could you please check the following:
1. Are you entering item_id in the form?
2.if there is some static data for the primary column being sent to db ?
Hi,
point 1 - No - it is primary key (number) it is not visible on form. It is not set by form/process model or any rule.
point 2 - No