Hello Folks,
I am getting this error while write to Data store entity.:"An error occurred while trying to write to the data store. No values have been written. Details: org.hibernate.PropertyValueException: not-null property references a null or transient value :"
Can anyone help me on this? Actually I want one column in a table is non nullable that is also behave as a foreign key.
Thanks
Discussion posts and replies are publicly visible
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.
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.
I kept it as it is. NOT NULL. It worked.
Yep, as long as you populate it before your first attempt to write a row, that'll work fine. The only reason you'd change this is if you wanted to write the row and then populate the FK later for some reason.
manjit.1486 said:I kept it as it is. NOT NULL
Glad to know, It's always error from process and the way it designed . Just remember don't use write to multiple datastore entity for writing new entry when there is Parent -child relationship
Okay, got it.
Hi Mike, I get the same error and all the FKs are NULL in my case. Can you look into this and suggest
The error message in your screenshot is something completely unrelated to the prior contents of this thread, as far as I can tell. It's also fairly self-explanatory.