Thanks Varun, that is exactly the solution. I believe that you should have the option of disabling ECAs when doing WebApp-Import Dir (or maybe for any import) to avoid a very nasty problem. I created a jira OFBIZ-5259 describing the issue, but basically, if you export an entire ofbiz installation, then later import it, all the ecas that run on operation="create-store" that create new records get ids from SequenceValueItem. This entity is overwritten when SequenceValueItem is imported. Later when you ask for a number, you get a "Failure in create operation for ..." with a duplicate key value.
In my case, the import of OrderPaymentPreference created millions of OrderStatus records with PAYMENT_NOT_RECEIVED. Then, when you try and create an order, you get the failure message above because the import of SequenceValueItem overwrote the changes made by the eca. -----Original Message----- From: Varun Bhansaly [mailto:vbhans...@gmail.com] Sent: Tuesday, July 09, 2013 11:36 AM To: user@ofbiz.apache.org Subject: Re: Unwanted OrderStatus when importing To disable EECA set entity-eca-enabled="true" in entityengine.xml's delegator definition. SECA may have to disabled by making a minor change in Java code AFAIK there's no setting to disable it. On Tue, Jul 9, 2013 at 11:55 PM, Skip <s...@thedevers.org> wrote: > I am importing millions of records from an existing system. Somehow, I am > getting multiple OrderStatus records with PAYMENT_NOT_RECEIVED for every > order imported. > > Firstly, does anyone know what eca is causing this, and second, is there a > way to disable all ecas while I import these records? > > Thanks in advance > > Skip > > -- Regards, Varun Bhansaly