Different request types (Create-Update, Update-Delete) in single ExecuteTransactionRequest or ExecuteMultipleRequest

(1) Share

Report

Posted on by Community Member

Hi,

I want to perform conditional updates on the CRM database. For this, I want to perform Create-Update and Update-Delete in a single transaction so that if anything goes wrong with the any request, everything will be rollback.

I am aware of Rollback. But my question here is on the executing a single transaction with multiple request ex. one with CreateRequest and 2nd with UpdateRequest. Can we execute these requests in a single transaction?

Something like below code:

var transReq = new ExecuteTransactionRequest()
{
    // Create an empty organization request collection.
    Requests = new OrganizationRequestCollection(),
    ReturnResponses = true
};

var account = new Account()
{
    Name = "Acme, Inc."
};

var createReq = new CreateRequest
{
    Target = account
};

transReq.Requests.Add(createReq);

account.NumberOfEmployees = 100;

var updateReq = new UpdateRequest
{
    Target = account
};

transReq.Requests.Add(updateReq);

var response = (ExecuteTransactionResponse)svc.Execute(transReq);

Any thoughts or ideas to achieve this?

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (1)

Emre GULCAN 2,379 on at

Like (0)

Report

Hi,

According to SDK notes all process rollback if any exception occured. You can find details on https://msdn.microsoft.com/en-us/library/gg328075.aspx

"Should any one of the requests fail and the transaction is rolled back, any data changes completed during the transaction are undone. In addition, a ExecuteTransactionFault is returned identifying the index into the request collection of the request message that caused the fault."

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Sure Gulcan, I am aware of Rollback. But my question here is on the executing a single transaction with multiple request ex. one with CreateRequest and 2nd with UpdateRequest. Can we execute these requests in a single transaction?

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

ExecuteTransactionRequest will execute all requests in the same transaction. If one request fails, all others will be rolled back

ExecuteMultipleRequest will execute each request in its own transaction, so there is no rollback for all requests. If one request fails, what happens after depends on what you pass to the ContinueOnError parameter

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Sorry if my question is misleading. Please have a look for updated question for better understanding.

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

Is there a problem with your code? Looms like it should do exactly that - execute both requests in the same transaction

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

Sorry.. I get it now.. if you create a record and want to update it after.. try setting the Id in your code..

Account.id = Guid.NewGuid()

Not recommended, in general, but should work.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes Sir, in this case yes it is having a problem. Because 2nd request will not be able to fetch the ID created in request 1. But is there any way that we can even execute transaction in 2 different entities?

i.e. req1 will be Create request on Account entity while req2 will update the existing record of Contact entity.

If yes that we can do it... then can you please let me know how to do that?

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (0)

Report

Think I just explained it above..

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes I saw that but there was a comment you have added not recommended so I thought to ask a little different approach in my question, to try with different entity. Would you please go through that comment and let me know if it is possible, please.

Thank you,

Pratik Soni.

Was this reply helpful? Yes No
Verified answer

ashlega 34,477 on at

Like (1)

Report

It's not recommended because crm is using sql guid generation.. some kind of optimization is happening there.. other than that, it should work. I don't think you can do it any other way since you will need to get that good for the update/delete, and you won't be able to. Can only assign it in advance.

Was this reply helpful? Yes No