SetState Vs ConfirmOrderAsync?

Questions
1

Hello,

If I use PlaceOrderAsync to place an order with the flag Confirm set to false and then later manually set its state to “Confirmed,” will that be equivalent to calling ConfirmOrderAsync directly?

Or is there additional processing happening behind the scenes with ConfirmOrderAsync that I might miss by setting the state manually?

So doing this:

var orderInformation = new PlaceOrderArgs
{
    Comments = "hello world",
    Confirm = false
};

await cartContext.PlaceOrderAsync(orderInformation);
// do stuff between
_stateTransitionsService.SetState<SalesOrder>(order.SystemId, OrderState.Confirmed);

Instead of this:
cartContext.ConfirmOrderAsync();

The main reason I want to bypass the standard “ConfirmOrderAsync” is that I need to modify order details after the fact. I need to correctly assign them to the appropriate organizations. Although I have a panel designed for this purpose, I’m encountering a database error because the system doesn’t allow changes to order data once confirmed.

Thanks in advance.

2

The PlaceOrder method is called by the payment app to create the order on confirmation, this is also persisting the order to the database.

The ConfirmOrder method is called by the developer to say that I want to create an order for this cart context.

So if you manually calling the PlaceOrder method, then you are creating the order without knowing that the payment app is accepting the order and this may lead into other issues, example that the order can missing transactions that make it hard to do payment operations.

After the order is placed, the cart should not be changed to avoid that cart and the order will be out of sync of each other. For your panel, you should not use the cart context at all, instead you should use the OrderService.Get to fetch the sales order and modifying that before calling OrderService.Update but be sure that you know what you doing with the order because it easy to make changes to the order that will create problem with post-purchase operations (capture etc).

In your case if you only want to assign the correct organization it may be better to do that before the order is created with the cartContext.AddOrUpdateCustomerInfoAsync.

1 Like
3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.