With the advent of econnect, such tools as dynamics gp integration manager, being transferred to the econnect site, created a truly normal environment for the client, the great plains programmer or the technical consultant. gl advanced windows huge, and unusual data migrations and modifications. The methods described here have become affordable to the maximum for the long-standing integration manager connectors, but people have not become practical, and econnect has not yet allowed the speed and speed of integration in principle. Using the econnect integration, you can only go through 10 operations per second, because econnect calls encrypted sql stored procedures, compared to the gp logic check in the ole-managed forms of great plains dexterity in the worn-out versions of im. Consider a script if you need to turn a year-round summer of gl records for a solid organization with different thousands of operations per week. 1. Export the information in tab-delimited or comma-delimited text, and import the firewood to microsoft sql server in intermediate table formats. Subsequently, massage the materials, we have: remove the quotation marks, for example, to where the visitors have the debit and loan fields. 2. Advanced odbc queries that are based on the odbc sql driver. Then you can put dynamics gp dsn for elegance. In the case when you still tried to group, aggregate information in odbc queries made from a text driver, then for sure, or became the most disappointing practice. 3. The gl header resource. 4. The primary source of the gl lines. Only use the select star operator from the existing sql view. 5. Save and use the integration. Take special note of why the econnect integration connector does not need to close all gp windows (how do you remember, an ole connector is required). 6. By now, you'll have to find yourself in a place where im will help you deal with the one you were creating in ended up with low-level insert scripts and apparently struggled with data integrity.
|