Discussion posts and replies are publicly visible
Please show us how the node input configuration looks like. Did you follow this?
https://docs.appian.com/suite/help/20.3/Write_to_Multiple_Data_Store_Entities_Smart_Service.html#example-inputs
Please check the link I posted and configure the input correctly.
Is there any reason why you use "writeToMULTIPLE Datae store entities"?Please check "write to data store entity.https://docs.appian.com/suite/help/20.3/Write_to_Data_Store_Entity_Smart_Service.html
As the name suggest: one is to save multiple values in potential multiple data store entities (of the same data store).The other one is to save into one Data store.___________________________________________________________________________if you want to use the Multiple node read the following:Requirements: you need an already created and maintained datastore with the suitable entity (CDT,Table).to explain it more detailed:currently you inserting just a process variable.The data store cannot understand random values. Every function in appian needs a specific structure. Data stores as well.A "write to data store entity" needs definied the entity aka location, where to save, and the data in a very specific structure. Please use the CDT structure you want to save. The CDT used in the data store and CDT of the data you want to save have to match.check the article stefan linked. The structure for "value" has to look like this:
1 2 3 4 5 6 7 8
={ {entity:pv!ENTITY_OPPORTUNITIES, data:{pv!RadiationOpp,pv!NewBusinessOpp}}, {entity:pv!ENTITY_ACCOUNT, data:{pv!AcmeAccount}}, {entity:pv!ENTITY_AE_NOTES, data:{pv!ListOfNotesFromAccountExec}} }
Hints: 1.) perhaps you create a constant for the entity first. Not necessary, but I would recommend it. so you have a smoother structure2.) perhaps you create a rule. you can insert the pure code into the "value" field, but its more "clean" with a rule.You insert your process data as rule inputs and you call the constant with the data store in it
Solution without rule; written in the value field:
{ entity: cons!EXA_MY_ENTITY_CONSTANT, value: pv!my_process_variable_to_save }
value:
rule!EXA_myDataStoreRule( my_process_variable_as_rule_Input: pv!my_process_variable_to_save )
Rule content:
{ entity: cons!EXA_MY_ENTITY_CONSTANT, value: ri!my_process_variable_as_rule_Input }