eConnect is slow on purpose because its running the transactions through business logic rules to make sure the transactions make sense and a lot of eConnect procedures are validating the data for instance it's making sure that the actindx used for a journal entry is in fact an account number already in the system. So the slowness in that fact is because it's there to CYA :) As for updating it quicker you can always import your data into a staging table in SQL by copying and pasting it and then running an insert into your GP table based on the data in the staging table. That'll be super fast but again, you need to know what tables eConnect is trying to hit so you don't miss anything. I would do this with EXTREME CAUTION, preferably in a test environment to make sure you get it right because if you create header records without detail records or vice-versa, you'll be in for a big headache down the road.
↧