Add/Update Action not writing to DSE

Can you please verify the CDT is same as a table. For example, all column properties need to same.
- Plus save the output in CDT again and see the value is saving back in CDT or not.
- Verify primary key is properly Define in CDT structure.

@sarah can you share the DSE node input as well as Output tab configuration, also the process variables which you are referring into DSE node

Make sure you map the output of the Write to DSE node back to your CDT so you can see if the primary key is being properly generated and stored. You can also use process history to to track changes to your process variables to ensure they are being passed and updated properly.

As per my understanding @sarah is missing the Data Tab input value of type CDT which needs to be persist into the DB, because as per the statement of @sarah, the process is running well and specially nothing appeared in DB, that means the data is not getting send properly from the input tab to be persist into DB.

Also i agree with @bryant.st39 to have output for understanding whether the data is getting persist and it's PK is getting generate properly or not.

@Sarah As i mention above also, it's better if you can attach the node configuration of Data Store Entity Node i.e. DSE node input as well as Output tab configuration, also the process variables which you are referring into DSE node, so that the practitioner can trace out the problem

For reference please refer the attachment of having wrong configuration in DSE, which gets published well but saves nothing in DB.

Thanks for all the input. @aloks176 - see the attached configurations. I checked all the input and output configurations and the process variables to ensure it's referring to the correct DSE. I'm not sure how to track the changes of the process variables to ensure they are being updated properly?

You can track changes to PVs thru the /designer interface. Find the process instance you are investigating, click "Process Details", click "Process History"...from there you can see each action in the system and the changes to PVs.

@bryant.st39 - ah yes perfect looks like that shows the error message - see attached screenshot. Can you suggest where to fix this error?

My guess is your PV is null. Since it is null and not empty, Appian doesn't how to reference the id field. Based on what I see, here I also assume you haven't created an id yet. I assume "Add/Update Ref Data for " is part of the form or task name. You could do some null handling to see if the PV is null to avoid this error.

Adding to @bryant.st39 also try using index() function instead of using pv!referenceData.id so this won't throw any error if the property id or it's value not found(or having null), simply you can return {} like


index(pv!referenceData, "id",{})

that should handle this error