I am currently loading a TON of historical GL transactions into dynamics gp. the createEntity method seems to only allow me to create one transaction at a time, causing this process to be quite lengthy. Can anyone advise on how I can speed the process?
I can go into more detail if necessary. thanks!
*This post is locked for comments
Hi Frank,
You can use VKonnact for GL (With AA) import. Through VKonnact you can import 1K (Approx.) GL entries in 60 sec time.
Also, VKonnact has its own data validation engine to validate & Correction data before importing.
You can use VKonnact for 15 days without spending single penny.
Thanks,
Govind
Multi-thread your code. SQL can handle it...
No, Integration Manager will not be faster than using eConnect because all Integration Manager uses is eConnect stored procedures. Any third part application for integration such as SmartConnect from eOne and SCRIBE all use eConnect procedures, that's the standard for GP business logic integration. It must validate each record line by line which is why it can be slow when importing large sets of data.
Is it though? IM leverages eConnect precedures. I am interacting directly with the eConnect procedures - I can't imagine how adding another layer could speed the process. I suppose I could be wrong though.
HI.
Try integration manager.best in speed with validation.
Tom, thanks for the response.
so if going the SQL route, what is the validation for a successful load - checklinks? it'll be simple backup, load, and restore if necessary. but again, how to validate to 100% confidence?
Also, we are using Analytical Accounting and if you're familiar those tables can get pretty large and only reference by ID. it'd be another challenge but doable. I think there is a separate checklinks for AA if I am not mistaking.
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.
Share
Report
All responses (
Answers (
617
