Write to multiple datastore entity

Writing to a datastore will always update the full row. This is in contrast to Appian Records, where only the provided fields will be updated.

, Is there any way so that only required columns are updated in a row, not the full row.

Rahul009 - You can create another CDT with only the required columns you intend to write (steps - download the current CDT XSD, remove the unwanted column definitions, change the name of the CDT and create a new one with this file). Create a data store entity for this CDT.

When you try writing using this new entity, only the required columns of the existing row will be updated.

Note: Use this approach only when it is extremely necessary(when you don't want to bring unwanted columns with huge data into process models).

Please explain exactly what you mean by that? Are you talking about the time it takes to execute the DB update, or about the time it takes for the node to complete?

Thanks Selvekumar, Will the table remain same and only the new CDT to be created?

Yes Stefan, it is the time it takes for the node to complete.

That has nothing to do with the actual DB update. This is the way how Appian scales to millions of active process instances compromising single node completion time.

Yes, the table will remain the same.

Can you please explain it a more. Any other way to resolve this?

I doubt that having a smaller CDT will make much of a difference in the time to execute. You need to look at the overall process design.

What is your specific issue with this behaviour?

The node consumes much time while writing to DB when the data is large.

The node consumes much time while writing to DB when the data is large.