Locking Cartage Grid on Sales Order.

[Ernst]

On JIWA721.

We dont want users to use Cartage 2 and 3 Only the top cartage line in Sales Orders.Have put this piece of code into LoadForm, ReadSalesOrder, Copy Sales Order, and CreateEnd

Works great for LoadForm, ReadSalesOrder, Copy Sales Order, but refuses to work for CreateEnd, which is probably the most important one, when they are making a new order and entering freight.
Is there something special to do to get it to work in New Sales Orders?

Code: Select all

      Dim salesOrderForm As JiwaFinancials.Jiwa.JiwaSalesUI.SalesOrder.BaseSalesOrderEntryForm = DirectCast(salesOrder.Client, JiwaFinancials.Jiwa.JiwaSalesUI.SalesOrder.BaseSalesOrderEntryForm)
      salesOrderForm.grdCartage.LockRow(1,True) 
      salesOrderForm.grdCartage.LockRow(2,True)

[SBarnes]

Without seeing the entire code it's hard to comment but that's not going to help you anyhow as every time a line on the sales order changes display line gets called which in turn calls Display cartage which goes and sets locked cells etc. on the grid.

You might be better going after the property change event on the sales order and just resetting the value to zero, if its been set to a value.

[Mike.Sheen]

As Stuart mentioned, a display of any line will cause the cartage grid to be redisplayed (and locked / unlocked) via the DisplayCartage method - so you'll need to add handlers for everywhere that results in the DisplayCartage method being called directly or indirectly.

These are the properties that I've identified you'll need to handle and lock your cartage grid rows in:

• SalesOrder.SalesOrderLineAdded
• SalesOrder.SalesOrderLineChanged
• SalesOrder.SalesOrderLineRemoved
• SalesOrder.Created
• SalesOrder.Read
• SalesOrder.Copied
• SalesOrder.Deserialized
• SalesOrder.PropertyChanged

Note that there might be some overlap in the events - such as when you add a line to a sales order you'll get both the SalesOrder.SalesOrderLineAdded event and the SalesOrder.PropertyChanged event - so you probably don't need to be handling both, but it'll ensure consistency in behaviour if you do.

Note also that the permissions system will also come in after any handling of events and displaying by the form and lock things based on permissions - your plugin will likely be adding handlers in the Setup rather than the SetupBefore plugin class, so if you choose to unlock anything you may be circumventing any permissions applied - you probably only are locking, but I just thought I'd mention that in case you were doing some unlocking of grid cells.

[Ernst]

Thanks Mike and Stuart. It looks like the code is going to be overloaded switching the grid off everytime, and I still may not catch all the cases.
Ive tried stuart suggestion and just made it zero if they try and put something in there. Should be good for now.

Code: Select all

SalesOrderHistorys_Changed

      If (e.PropertyName = "CartageCharge2" And SalesOrderH.CartageCharge2.ExGSTAmount <> 0) Or (e.PropertyName = "CartageCharge3" And SalesOrderH.CartageCharge3.ExGSTAmount <> 0 ) Then
         Msgbox ("Freight Charge Lines 2 and 3 should not be used at Lube, please use top Courier line ")
         SalesOrderH.CartageCharge2.ExGSTAmount = 0
         SalesOrderH.CartageCharge3.ExGSTAmount = 0         
      End If

[Mike.Sheen]

It looks like the code is going to be overloaded switching the grid off everytime

Nonsense. If you try it, you'll see that the inefficiency of locking rows repeatedly is not noticeable - microseconds per invocation.

[SBarnes]

I am not sure how you are going to miss something given Mike gave you the list but the attached should do what you need.

[Ernst]

OK thanks, will give that a go..Thanks for help

[Ernst]

That plugin works perfectly Stuart Thx

[SBarnes]

You are welcome, but Mike did the initial heavy lifting by providing the list of events.