Storing multiple data entities in single transaction

Question

I have one form in that i have to store data into 4 CDTS .Project ,projectteaam,milestone,milestonetask, 
 ={{entity:pv!DSR_Project, data:{pv!DSR_Project.projectname,pv!DSR_Project.roleid,pv!DSR_Project.clientid,pv!DSR_Project.estimatedbudget,pv!DSR_Project.projectstartdate,pv!DSR_Project.projectenddate,pv!DSR_Project.description}},{entity:pv!DSR_ProjectTeam, data:{pv!DSR_ProjectTeam.projectid,pv!DSR_ProjectTeam.employeeid,pv!DSR_ProjectTeam.startdate,pv!DSR_ProjectTeam.enddate,pv!DSR_ProjectTeam.description}},{entity:pv!DSR_MileStone, data:{pv!DSR_MileStone.projectid,pv!DSR_MileStone.milestonename,pv!DSR_MileStone.startdate,pv!DSR_MileStone.baseline,pv!DSR_MileStone.forcast,pv!DSR_MileStone.actual,pv!DSR_MileStone.estamount,pv!DSR_MileStone.actualamount,pv!DSR_MileStone.comments,pv!DSR_MileStone.paymentrecieveddate}},{entity:pv!DSR_MileStoneTask, data:{pv!DSR_MileStoneTask.milestoneid,pv!DSR_MileStoneTask.taskname,pv!DSR_MileStoneTask.taskhour}}}

can any one help me out of this .I need to store data in multiple data store entities.since im unable to store

rickyc0004 · Accepted Answer

You might want to create a constant for each entity and use in place of process variable. Also you do not need to mention each field in data just a process variable with right data type (CDT) will write the data to entity. 
 { { entity: cons!DSR_PROJECT_ENTITY, data: pv!DSR_Project }, { entity: cons!DSR_PROJECTTEAM_ENTITY, data: pv!DSR_ProjectTeam }, { entity: cons!DSR_MILESTONE_ENTITY, data: pv!DSR_MileStone }, { entity: cons!DSR_MILESTONETASK_ENTITY, data: pv!DSR_MileStoneTask } }

Vadivelan · Answer

Hi gangadharr0001 
 You can follow the below structure for writing to multiple data store entity. Your pv should be of cdt type where you can store all the individual field data. { 
 {entity:cons!ENTITY_PROJECT,data:pv!Project}, 
 {entity:cons!ENTITY_PROJECT_TEAM,data:pv!projectteaam}, 
 {entity:cons!ENTITY_MILESTONE,data:pv!milestone}, 
 {entity:cons!ENTITY_MILESTONE_TASK,data:pv!milestonetask} 
 } Documentation: https://docs.appian.com/suite/help/20.3/Write_to_Multiple_Data_Store_Entities_Smart_Service.html#example-inputs

Mike Schmitt · Answer

Your data PV's will need to be populated with data beforehand for this to work. You'll need to troubleshoot your SAIL form and/or the configuration in which your form is passing data back to the process.

Mike Schmitt · Answer

Please provide some further details (screenshots etc) of your user input task's Data Inputs tab as well as the Form configuration. Those are the things we need to see to verify whether it'd be expected to work. 
 Per your screenshot above it looks as if your DSR_Project PV is populating with some valid data. We can't tell much about the others based on what you've provided so far.

Mike Schmitt · Answer

Your screenshot looks fine. For your code, you can remove the entire saveInto of your submit button basically - if the data is being saved into the RI values by the form fields, there is no need to save them again on Submit click - this will do nothing helpful and there's a slight chance it might break something. 
 Can you confirm (in your Data Input configuration) that your other ACP variables are being set to save into PVs? The way DSR_Project is configured in your screenshot above is correct. Also can you show us any configurations in the Data Outputs tab?

Mike Schmitt · Answer

In this case you will need to write DSR_Project separately in its own WTDS node prior to the others. The outputs of the WTDS node should save the saved value back into the DSR_Project PV. 
 Then after that node, you can place a script task node where you populate the autogenerated projectId into the appropriate spots in the other CDTs. 
 Then finally, do your multi-DS write (excluding the DSR_Project pv, assuming no additional changes have been made to it). 
 Mocked-up screenshots for clarification:

Storing multiple data entities in single transaction

Top Replies