KB-2299 Write Records smart service fails when writing record with null primary key to SQL Server

Ryan Good — Thu, 21 Mar 2024 19:41:33 GMT

Current Revision posted to Appian Knowledge Base by Ryan Good on 3/21/2024 7:41:33 PM

Symptoms

If the target database type is SQL Server, the Write Records smart service will fail when writing a new record with a null primary key. The following error will be seen in the process history and tomcat-stdOut.log:

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

In 23.4, the Write Records smart service was updated to allow non-nullable foreign keys. This changed how the Write Records smart service decides what needs to be an INSERT vs. an UPDATE query in the database.

As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model.

Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being explicitly defined as the primary key value in the SAIL code or process model.

Affected Versions

This article applies to Appian 23.4 and later.

Last Reviewed: March 2024

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

Ryan Good — Thu, 07 Mar 2024 22:44:34 GMT

Revision 11 posted to Appian Knowledge Base by Ryan Good on 3/7/2024 10:44:34 PM

Symptoms

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model.

Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being explicitly defined as the primary key value in the SAIL code or process model.

Affected Versions

This article applies to Appian 23.4 and later.

Last Reviewed: March 2024

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

Ryan Good — Thu, 07 Mar 2024 22:39:25 GMT

Revision 10 posted to Appian Knowledge Base by Ryan Good on 3/7/2024 10:39:25 PM

Symptoms

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model.

Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being explicitly defined as the primary key value in the SAIL code or process model.

Affected Versions

This article applies to Appian 23.4 and later.

Last Reviewed: March 2024

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

Ryan Good — Thu, 07 Mar 2024 22:37:38 GMT

Revision 9 posted to Appian Knowledge Base by Ryan Good on 3/7/2024 10:37:38 PM

Symptoms

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model.

Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being explicitly defined as the primary key value in the SAIL code or process model.

Affected Versions

This article applies to Appian 23.4 and later.

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

Ryan Good — Thu, 07 Mar 2024 20:35:06 GMT

Revision 8 posted to Appian Knowledge Base by Ryan Good on 3/7/2024 8:35:06 PM

Symptoms

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model.

Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being explicitly defined as the primary key value in the SAIL code or process model.

Affected Versions

This article applies to Appian 23.4 and later.

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

lyann.sun — Mon, 26 Feb 2024 18:40:59 GMT

Revision 7 posted to Appian Knowledge Base by lyann.sun on 2/26/2024 6:40:59 PM

Symptoms

If the target database is SQL Server, the Write Records smart service will fail when writing a new record with a null primary key. The following error will be seen in the process history and tomcat-stdOut.log:

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model.

Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being explicitly defined as the primary key value in the SAIL code or process model.

Affected Versions

This article applies to Appian 23.4 and later.

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

lyann.sun — Mon, 26 Feb 2024 17:15:38 GMT

Revision 6 posted to Appian Knowledge Base by lyann.sun on 2/26/2024 5:15:38 PM

Symptoms

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model.

Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being defined as the primary key value.

Affected Versions

This article applies to Appian 23.4 and later.

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

lyann.sun — Mon, 26 Feb 2024 17:15:16 GMT

Revision 5 posted to Appian Knowledge Base by lyann.sun on 2/26/2024 5:15:16 PM

Symptoms

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

In 23.4, the Write Records smart service was updated to allow non-nullable foreign keys. This changed how the Write Records smart service decides what needs to be an INSERT vs. an UPDATE query in the database. As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model.

Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being defined as the primary key value.

Affected Versions

This article applies to Appian 23.4 and later.

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

lyann.sun — Mon, 26 Feb 2024 17:11:59 GMT

Revision 4 posted to Appian Knowledge Base by lyann.sun on 2/26/2024 5:11:59 PM

Symptoms

If the target database is SQL Server. the Write Records smart service will fail when writing a new record with a null primary key. The following error will be seen in the process history and tomcat-stdOut.log:

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

In 23.4, the Write Records smart service was updated to allow non-nullable foreign keys, which changed how the Write Records smart service decides what needs to be an INSERT vs. an UPDATE query in the database. As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL code or the process model. Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being defined as the primary key value.

Affected Versions

This article applies to Appian 23.4 and later.

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

lyann.sun — Mon, 26 Feb 2024 17:10:30 GMT

Revision 3 posted to Appian Knowledge Base by lyann.sun on 2/26/2024 5:10:30 PM

Symptoms

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

In 23.4, the Write Records smart service was updated to allow non-nullable foreign keys, which changed how the Write Records smart service decides what needs to be an INSERT vs. an UPDATE query in the database. As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is explicitly defined to be NULL in either the SAIL or the process model. Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being defined as the primary key value.

Affected Versions

This article applies to Appian 23.4 and later.

KB-XXXX Write Records smart service fails when writing record with null primary key to SQL Server

lyann.sun — Mon, 26 Feb 2024 17:07:37 GMT

Revision 2 posted to Appian Knowledge Base by lyann.sun on 2/26/2024 5:07:37 PM

Symptoms

Unable to write to or delete from the source due to a data integrity violation. 
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

In 23.4, the Write Records smart service was updated to allow non-nullable foreign keys, which changed how the Write Records smart service decides what needs to be an INSERT vs. an UPDATE query in the database. As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is null. Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being defined as the primary key value.

Affected Versions

This article applies to Appian 23.4 and later.

Write Records smart service fails when writing record with null primary key to SQL Server

lyann.sun — Tue, 20 Feb 2024 17:46:19 GMT

Revision 1 posted to Appian Knowledge Base by lyann.sun on 2/20/2024 5:46:19 PM

Symptoms

If the target database is SQL Server. the Write Records smart service will fail when writing a new record with a null primary key. The following error will be seen in the process history:

Unable to write to or delete from the source due to a data integrity violation.
Error Details: Cannot insert the value NULL into column <column>, table <table>; column does not allow nulls. INSERT fails.

Cause

In 23.4, the Write Records smart service was updated to allow non-nullable foreign keys, which changed how the Write Records smart service decides what needs to be an INSERT vs. an UPDATE query in the database. As a side effect, due to how the SQL Server IDENTITY columns work, the Write Records node fails if the primary key is null. Please note this only applies if it is a SQL Server database.

Action

Update the design to prevent NULL from being defined as the primary key value.

Affected Versions

This article applies to Appian 23.4 and later.