An error occurred while trying to write to the data store . No values have been written. Details: org.hibernate.

You have columns in database which are defined as Non-Nullable. Which means it cannot be empty and looks like you have no value being saved, hence the error. Please share the DB structure and the PV data if possible.

Please see db structure:

Valuationid is not null field as it should not be empty or null.

Don't use Write to Multiple Datastore entities when there is a Parent-Child relation. I don't think it has the leverage to auto map Foreign keys like Write records.

Here is the approach you need  follow

1. Write to Parent table first , Use stored values and map the FK and then write to child

Working with flat Cdt's

I have modified process. But it didn't work as expected. In valuation table id column is autoincremented and primary key.
In valuation doc table valuationid column is foreign key

manjit.1486 said:

valuationid column is a foriegn key

yeah, appian doesn't care and it won't happen automatically - you'll either need to manually populate it in your CDT prior to writing, or change the column to NOT NULL (edit: sorry, that should have been, change to NULL) and populate it later.

Column is already a NOT NULL

manjit.1486 said:

But it didn't work as expected.

your modified process flow looks correct.  are you capturing the written "valuation" value back to the PV?  This *must* be done via the "stored values" setting in the Outputs tab.

It worked. Thanks for help.

1.In Write to Valuation output tab save back what has been written . Use same Pv (Parent table variable)

2. in Script task

stored as pv!caseDocument.valuationid

then write it

manjit.1486 said:

Column is already a NOT NULL

What he meant is make it NULL 

manjit.1486 said:

Thanks for help.

Glad to hear that.  As an aside, please go ahead and up-vote and/or "verify answer" on any/all answers (like from me and Venkat in particular) that you found most directly helpful.

Venkat Avuluri said:

What he meant is make it NULL 

oops, yup my bad

Yes,  I am doing the same. Actually when I copied the node I forget to remove from the input tab. It works perfectly now. Thank you so much.

Yes,  I am doing the same. Actually when I copied the node I forget to remove from the input tab. It works perfectly now. Thank you so much.