webERP Forum

Full Version: Inconsistency caused by cancelling an order
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

I've noticed that when I cancel an Order for a customer it causes the system to try an use the first blank primary field in salesorder to create a new order. That's all fine, if it wasnt for some inconsistency in the database telling the user that the primary is being duplicate. That happens from the lowest "available" primary slot in the slaesorder table each time an order gets cancelled. So for example if you cancel 10 orders, the system will tell you for the next 10 times you try to create a new order that "primary is duplicate for whatevernumber" before it gets to the point where it creates an order for an actual free primary.

My guess is that the primary from salesorders is still in use as foreign key for another table and therefore causing that inconsistency.