SAP MDK - how does context work in change set.

Ratnakar,

The ChangeSet Action allows you to define a "group" of transactions that must all succeed together. Meaning that if one transaction in the change set fails then all the other transactions are not applied.

Can you elaborate on what your multiple create actions are doing? Are they really related creates? If yes the ChangeSet would be appropriate to use. If they are really independent then you can just call CreateEntity multiple times as needed.

--Bill

Execute Action returns a promise which means the actual execution will occur but in an async way. Since you are looping and calling the same action, you will need to be very careful about where you data values are coming from. I am assuming you are referencing some of them from Client Data for the user specific values. This can be problematic since client data will be evaluated when the action actually executes by which time the value you really wanted to use may have changed.

We introduced action overrides in MDK 4.3 to address this. You will want to take advantage of this to directly pass the employee specific values to your create action.

In terms of knowing when all the creates are done, since the execute action returns a promise, you can build an array of all the promises returned and then wait for them to be completed before displaying your message.

createPromises = [];
for(i = 0 ; i < employee.length ; i++ ){
  context.getClientData().employee = employee[i];
  GenerareLocalId(context).then(localNumber => {
  context.getClientData().localNumber= localNumber;
  createPromises.push(context.executeAction("....Confirmation.action"));
})
}
//Wait for all create actions to be executed
return Promise.all(createPromises).then(results=> {
  return messageAction;
}