Storing multiple data entities in single transaction

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

Vadivelan and rickyc0001 ,

As per you guys suggestion i did but in variables value showing no value .Please look at images

Verified SAIL form ,process model executing fine but its not updating process variables .only saving data in project entity remaining entities storing null values .and also projectteam,milestone ,milestonetask  is child tables of project .Can you give suggestion on this

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.

As per your request user input data and user input form.Please look t once 

Thanks

mike schmitt

Can you give me suggestion on above post

Thanks

Please find below post regarding above issue

Just to confirm - you showed the project variable in your screenshot of the user input task, and it appears that one is saving data to your process correctly. Are you doing the same thing (using a saveInto in the inputs of your user input task) for the other variables?

Also, is it possible that your form isn't saving the data correctly? If you go to the interface and submit the form from Interface Designer, do you see the rule inputs populated with data you expect?

Peter Lewis

buttons: a!buttonLayout(
primaryButtons: {
a!buttonWidget(
label: "Submit",
value: {
ri!DSR_Project,
ri!DSR_ProjectTeam,
ri!DSR_MileStone,
ri!DSR_MileStoneTask
}, saveInto: {
ri!DSR_Project,
ri!DSR_ProjectTeam,
ri!DSR_MileStone,
ri!DSR_MileStoneTask
},
submit: true,
style: "PRIMARY"
)
},
secondaryButtons: {
a!buttonWidget(
label: "Cancel",
value: ri!cancel,
saveInto: ri!cancel,
style: "NORMAL"


)
}
)

Can you check this code and screen shot .in the rule input its populated the data

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?

Thanks Mike schmitt 

I removed  saveinto from submit button  now it is storing in all entities .But Projectid not updating in Projectteam since Projectid is foreign key in Projectteam  and also in Milestone cdt also projectid is foreign key and in milestonetask  cdt  projectid and milestoneid foreign key 

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:

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:

I'm able to see projectid in stored values and im assigning projectid to projectteam entity in script task .but im unable to map 

Please look at configuration once  any changes required Please let us know .

In the script task , why are you mapping project ID to DSR_project team type variable ? Also please check the type of your Project ID . 

because projectid i want to store in projectteam cdt 

Try save into projectteam.projectId. Also , Please check Project ID type (Number ).

Thank you so much Mike Schmitt

Thanks for the support guys finally Its working .