Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
I have the Outputs tab of a Write to Data Store Entity setup where AC!StoredValues is stored as the process variable (PV) that I'm inputting. The data is successfully written into the DB, but the id is not saved back to the PV.
I don't see a "Modify Variable" or similar activity being done after/during the Write to DSE action.
As a workaround, I've made a custom output to store ac!StoredValues.id into a new pv!id. This works and I use a script to save it to the original PV.
Am I missing something in my attempt to save the entire AC!StoredValues into my PV? Like does it need to be cast or only work with certain datatypes?
Discussion posts and replies are publicly visible
As long as your process variable is of the same data type you're writing to the database it should work. One thing to check is to make sure on the CDT you have your primary key set to auto-increment
All of those have check out. CDT and Cloud DB table have the primary key set to auto increment.
By any chance, how is your setup on the inputs tab? Could it be that you defined a save into for the data to be stored? If yes, remove this as it will conflict with the output definition.
Thank you! I wasn't aware that there would be a conflict for this. Removing it has worked for me.
The documentation doesn't address this potential issue docs.appian.com/.../Write_to_Data_Store_Entity_Smart_Service.html
Just above this link is a yellow box given a hint
https://docs.appian.com/suite/help/21.1/Process_Node_and_Smart_Service_Properties.html#saving-activity-class-parameters-to-process-variables
I gave a lot of Appian trainings. This is always something I let trainees trap into to never do that mistake again. A save into in the input tab conflicts with definitions in the output tab. And on both tabs, the order does NOT define the order of execution.