Hello,
Think my situation is a bit more complex.
In general we will be building third party solutions for my customers using GP data. For loading data into GP the eConnect and Web Services is the best method (validation, business rules, etc). We don’t want the customer to incur additional costs to use our solution either. Also interested in the solution selection when the SaaS version comes out.
(I think that for the long term a mix of ODBC (Direct DB access) and eConnect with web services may be the way to go.) One point is that For export from GP there seems to be:
1) Dexterity
a) Delivering an integration - An integration can be installed by any Microsoft Dynamics GP customer.
b) More features than what is needed
c) Additional installation required
2) Modifier with VBA
a) Delivering an integration - An Integration can be installed by any Microsoft Dynamics GP customer that has purchased Modifier with VBA or the Customization Site License.
b) Out – requires purchase from the customer
c) Additional installation
3) Visual Studio Tools for Microsoft Dynamics GP
a) Delivering an integration - An integration can be installed by any Microsoft Dynamics GP customer.
b) Additional installation
4) Continuum
a) Delivering an integration - An integration can be installed by any Microsoft Dynamics GP customer.
b) Additional installation
5) eConnect
a) Delivering an integration - An integration can be installed by any Microsoft Dynamics GP customer that has installed the eConnect runtime components.
i) Note – need to understand penetration of eConnect Customer in MSDGP installations
ii) Additional installation but I assume this has a high penetration at the customer sites
b) Open issue – with the SaaS version of GP will this require an additional installation?
6) Web Services for Microsoft Dynamics GP
a) Delivering an integration - An integration can be installed by any Microsoft Dynamics GP customer that has installed the Web Services for Microsoft Dynamics GP runtime components. (Requires eConnect)
i) Additional installation
b) Open issue – with the SaaS version of GP will this require an additional installation? Assume not.
i) Note – need to understand penetration of “Web Services for Microsoft Dynamics GP runtime components”
(1) Note - Need to understand the fit of the solution with the existing GL extraction (metadata and data)
(a) Fields in GL3000 not covered (approximately 80% are)
(b) Table SY40101 not covered via web services (I think)
7) Integration Manager
a) Delivering an integration - An integration can be installed by any Microsoft Dynamics GP customer that has purchased a license for Integration Manager.
i) Out – requires that customers purchase an additional component
8) ODBC
a) Delivering an integration - An integration can be installed by any Microsoft Dynamics GP customer
i) We know that most customers will have this.
ii) Database locking seems to be an issue.
iii) Not sure if this option is supported by GP by Microsoft
iv) Also the tables seem to change, added columns by release
v) 2015 will be SaaS and therefore this may not even be an option in the future.
vi) Difficulty in dealing with UNION tables (sample SQL)
Share
Report
All responses (
Answers (
24,406
