Developer forum

Hi Stephen

Default you cannot - since a user can be member of several groups.

You can use a Notifications.Standard.User.OnExtranetLogin notification which will fire when the user logs in - and then assign the customer number from one of the groups the user belongs to. This will ensure the user has the customer number and be used for pricing etc.

Another approach might be to add it on the cart using Dynamicweb.Ecommerce.Notifications.Ecommerce.Cart.Created notification.

You mean something like this in the OnExtranetLogin?

// Set CustomerNumber to the derived one
var user = Dynamicweb.Security.UserManagement.User.GetUserByID(userId);
user.CustomerNumber = custNo;

I have already code to get the customernumber from one of the parent groups. It returns the first one it finds. So I will inform the customer, they must not make the users members of multiple groups if those groups have a different customer number.

Unfortunately it doesnt work. And If i call the save() method on the user object, it does set the customernumber on the user, but this will not be available for an order unless the user logs in again, once its set.

Is there a session variable that is used when the order is sent? I want to set that instead

I will try this instead

/// <summary>
///  Gets the customernumber for the group, when creating cart, and sets the ordercustomernumber to this
/// </summary>
[Subscribe(Ecommerce.Cart.Created)]
public class OnCartCreated : NotificationSubscriber
{
    public override void OnNotify(string notification, NotificationArgs args)
    {
        if (!(args is Ecommerce.Cart.CreatedArgs))
            return;

        Ecommerce.Cart.CreatedArgs item = (Ecommerce.Cart.CreatedArgs)args;

        var user = Dynamicweb.Security.UserManagement.User.GetCurrentFrontendUser();
        var userId = user.ID;
        var custNo = Helper.GetGroupCustomerNumber(userId);

        item.Order.CustomerNumber = custNo;

    }

I ended up doing it in the Order BeforeSave event, and that seems to work. Gets called a lot though :(

Cool.

Yeah, that save is called too many times - we hope to get to a point where we can do that part better - and not break solutions that kind of rely on it... #DW10

What if I do this instead? Will it create some kind of race condition between the order being exported to xml and my aftersave operation modifying it? Is the db commit before or after "aftersave"?

 public override void OnNotify(string notification, NotificationArgs args)
 {
     if (!(args is Ecommerce.Order.AfterSaveArgs))
         return;

     Ecommerce.Order.AfterSaveArgs item = (Ecommerce.Order.AfterSaveArgs)args;

     var user = Dynamicweb.Security.UserManagement.User.GetCurrentFrontendUser();
     var userId = user.ID;
     var custNo = Helper.GetGroupCustomerNumber(userId);

    if (custNo.IsNotNullOrEmpty() &&  item.Order.CustomerNumber != custNo && !item.Order.IsCart)
 {
     item.Order.CustomerNumber = custNo;
     item.Order.Save();
 }
 }

It is not a good idea to call save inside a save notification subscriber as that can go wrong as that might trigger another notification.

So simply set the property onbefore save, but do not save it as that will happen as soon as your notification is exited. So beforesave, and do not call save.

Also you are missing a null check on the user instance - it could very well be null if you are not logged in or not in the frontend.

Ok thanks.