Actually I have lots of code via calls from their calls on soposd. I did some funky pricing for my last job. With TIW hooks the SOPSD gets really screwy. I needed to take the parts list that TIW generated from the user's order and then price that against the multipliers for that customer, by part type. This was manufacturing so there were only 20% of all orders were stock leaving 80% as custom configured.

Of course the multiplers were different by material type for that customer.

In the Sales Order that printes I had to show the breakdown of the configured part with MFG List price, the discount multiplier, and their net price, total it up and have that tie to the QTY + Extended price.

Ode to Joy.


If anyone knows what flag TIW uses to NOT fire the SO Confgurator I'd love to hear it. I still have issues with that code.

__Stephen


>You can run, but you can not hide. That answers the question about SO. I kinda figured out early on to only add a call in the button clicks to my stuff.
>
>PF
>
>>Damn the nightmares continue. :) The save on the SO is off the button in sopost, and you are on soposd.scx. One thing I remember is that you cannot really add "lots of code" to their events, but you can add your own method to the form and call it in the click()on the save button.
>>
>>__Stephen