Hey Graham,

The only reason I could think this would happen is if the order isn't assigned to the member. Currently this happens at two points, 1) when the order is created and 2) when the BeginPaymentForm method is called in the review step.

If your member logged in after the order was created then it wouldn't get assigned to them untill the payment review step, which might explain why it takes them needing to get to the review stage for the discount to apply.

Does this happen to all orders? ie, if you placed this order, and then started a new one when you know they are definitely logged in and the order is created after they are logged in. Or is it potentially only under this scenario where the order was created prior to login?

If it is the later, you might need to add something to your login routine that says if the member has a current order when they sign in, then assign the order to that member via order.AssignToCustomer(currentMember.Key.ToString())

Matt

Well the code I am to create an order is as follows, so I am using the the _sessionManager.GetOrCreateOrder() way.

When I get to it tonight I will track the CustomerReference and see if the order is assigned to the member or not when I hit the information page from the basket.

            var linesToAdd = AddToCartMapper.MapFormCollectionToAddToCartDto(model);

        try
        {
            foreach (var line in linesToAdd)
            {
                using (var uow = _unitOfWorkProvider.Create())
                {
                    var updateOrder = _sessionManager.GetOrCreateCurrentOrder(model.StoreId)
                        .AsWritable(uow)
                        .AddProduct(line.ProductReference, line.Quantity, line.ObjectToDictionary())
                        .SetProperties(new Dictionary<string, string>
                        {
                            { Constants.Properties.Customer.FirstNamePropertyAlias, model.FirstName },
                            { Constants.Properties.Customer.LastNamePropertyAlias, model.LastName },
                            { Constants.Properties.Customer.EmailPropertyAlias, model.EmailAddress },
                            { "billingAddressLine1", model.AddressLine1 },
                            { "billingAddressLine2", model.AddressLine2 },
                            { "billingAddressLine3", model.AddressLine3 },
                            { "billingAddressLine4", model.AddressLine4 },
                            { "billingCity", model.TownCity },
                            { "billingCounty", model.County },
                            { "billingZipCode", model.Postcode },
                            { "billingTelephone", model.PhoneNumber },
                            { "description", "Course Booking" },
                            { "companyName", model.CompanyName},
                            { "jobTitle", model.JobTitle}
                        });

                    _orderService.SaveOrder(updateOrder);

                    uow.Complete();
                }
            }
        }

Hey Matt,

So I have given this a try tonight and am outputting

@currentOrder.CustomerInfo.CustomerReference

on the information page of Vendr checkout and there is no value output, so it is definitely not persisting for some reason.

I have got around this for now by calling:

updateOrder.AssignToCustomer(Members.GetCurrentMember().Key.ToString());

just before I save the order when creating it for the first time as was shown in the previous post. I can confirm that now I am calling it manually that the customer reference is set correctly and discounts are applied.

If you find out what the issue is and create a fix, let me know and I will remove the manual piece of code.

Graham

is working on a reply...