After writing a new vehicle with auto-increment primary key using Write to Data Store Entity, how should you obtain the value?

After writing a new vehicle with auto-increment primary key using Write to Data Store Entity, how should you obtain the value?

• A. Reference the ac!StoredValues in the Outputs tab of the Write to data Store Entity node.
• B. Read the value directly from the database after the write.
• C. Use a separate Read from Data Store Entity node to fetch the key.
• D. The value is not available during the process.

Answer: (A)

When you write a new record to a Data Store Entity that uses an auto-increment primary key, Appian provides the generated key values right in the node’s outputs. The value you want is exposed as ac!StoredValues in the Outputs tab. Accessing those stored values immediately after the write gives you the actual primary key(s) assigned to the new record(s) without needing another database query. This is the straightforward, reliable way to obtain the new ID. Reading the database after the write or performing a separate read node is unnecessary and less efficient because the generated keys are already available from the write operation’s outputs. The claim that the value isn’t available during the process is incorrect—the key values are accessible as soon as the write node finishes.

When you write a new record to a Data Store Entity that uses an auto-increment primary key, Appian provides the generated key values right in the node’s outputs. The value you want is exposed as ac!StoredValues in the Outputs tab. Accessing those stored values immediately after the write gives you the actual primary key(s) assigned to the new record(s) without needing another database query. This is the straightforward, reliable way to obtain the new ID.

Reading the database after the write or performing a separate read node is unnecessary and less efficient because the generated keys are already available from the write operation’s outputs. The claim that the value isn’t available during the process is incorrect—the key values are accessible as soon as the write node finishes.