Changed Delivery Method does not "stick"

Hi everyone -happy Friday,

We're having a ship method selection problem.  When in an order with a specific MOS, if you change the ship method from the default for the MOS to an alternative (also associated to the MOS in TX_MOS_SHIP_METHOD!), it reverses back to the default after you go to select performances in the Line Item tab.  

The MOS can then be changed back to the non-default ship method selected previously, and the selection will stick for the remainder of the order.  But if one was to forget or not check the ship method again, it would flip to the default. Problem!

I process orders very rarely so I'm mostly relaying a coworker's difficulty - has anyone else experienced this?   In TR_ORDER_SHIP_METHOD, this ship method does not require an email or postal address, so that is not what's tripping us up.

Any ideas?

Thanks!

Frannie

Parents
  • Hi Frannie,

    We've found this as well and have instructed our reps to always choose delivery method at end of order (before paying for the order as we have fees attached to delivery methods).  We've never been able to figure out how to have it stick.

    Michele

  • Hi all,

    Thanks for your input - I am glad to know it is not just us.

    I will open a TASK ticket and let you know if there is a resolution.

    Have a good weekend - 

    Frannie

  • Hi everyone (specifically Michele!),

    I posted about this on TASK and it is not normal behavior.  Looks like it will happen if the HABO Foreign indicator for the MOS in question has a value of NULL or N.  I changed the HABO Foreign indicator to Y and did some testing - the ship method will now stick unless it is a ticket order for a constituent with a primary address that is foreign.  (this indicator is a tick box located in Campaigns > References > MOS)

    Sounds like the developers-that-be will be investigating what the problem is if HABO Foreign is set to N or NULL.  If I hear more I will post again.

    Hope this is helpful, 

    Frannie

Reply
  • Hi everyone (specifically Michele!),

    I posted about this on TASK and it is not normal behavior.  Looks like it will happen if the HABO Foreign indicator for the MOS in question has a value of NULL or N.  I changed the HABO Foreign indicator to Y and did some testing - the ship method will now stick unless it is a ticket order for a constituent with a primary address that is foreign.  (this indicator is a tick box located in Campaigns > References > MOS)

    Sounds like the developers-that-be will be investigating what the problem is if HABO Foreign is set to N or NULL.  If I hear more I will post again.

    Hope this is helpful, 

    Frannie

Children