To clarify: The API CD is supplied with the others, and I presume that is what you mean when you say that your IT guys have it. But it is not usable until you have asked for the API licence. In other words your licence file will have zeroes in the API line, and will have to be replaced with one that has the appropriate number of licences. In the example of Alex Wongs own licence file, he has 12 Named Users.
We may be talking about two different things. Ive referred to the API and its capabilities. If someone (and I know Primavera Australia is one) supplies software that makes integration easier, then that s/w would be at a cost. When Primavera is integrated with any other system, using the API, then someone has to do the work. (Even though all the "hooks" are there, and the data structure is well documented.) You may chose to do that yourselves, or contract it out. Or you may take advantage of someone else having already some or even all of that work. Perhaps that is what they are offering, you need to ask them.
I/We have lots of experience of the SDK and the API. As a company we build interfaces between work management systems, such as SAP and Maximo, to Primavera.
If you are an Excel guru who wants a cute single-user interface to Primvera the SDK is tolerable. If you want an industrial-strength multi-user interface that moves LOTS of data, the SDK is your worst nightmare.
The API is hard to use. You have to code in Java which is a special form of torture for us over 50s. It works. Code you create migrates from one version of Primavera to the next. DO NOT use the SDK for a "corporate" solution.
Member for
19 years 3 months
Member for19 years3 months
Submitted by Arthur Godbeer on Fri, 2006-09-08 03:35
Chris, even if there are no responses from API users in this forum , the API is certainly being used. Although the majority of users will have no need for it, there are many who do, and are doing. It is also used by Primavera partners who integrate their software with Primavera, including several who offer integration software to systems such as SAP.
The API is well documented, but someone has to do some programming.
Member for
20 years 5 months
Member for20 years5 months
Submitted by Chris Radecki on Thu, 2006-09-07 22:52
Sound like API is not being used. Sound like SDK might be the way.
Could not see how to export P3e Notebook Topics in Excel - can do it with the other Activity fields. Primavera (bless em) indicates that this may be an addon for the future!. Is there another way to get to Excel.
Looking at the Notebook Topic reports in HTML - seem to loose the formating on reporting.
Thanks for thetip.
Member for
19 years 3 months
Member for19 years3 months
Submitted by Arthur Godbeer on Thu, 2006-09-07 07:05
Neither the original API (ODBC, but observing the business rules) nor the newer one (XML) are charged for at present. They are both "delivered" on the CDs, but the XML API (on its own CD) is only useable after you have asked for it. It is not needed by most users, and is not initially included in your licence file. That is done on request, and requires the licence file to be amended.
Member for
19 years 3 monthsRE: Integration API - P3e
To clarify: The API CD is supplied with the others, and I presume that is what you mean when you say that your IT guys have it. But it is not usable until you have asked for the API licence. In other words your licence file will have zeroes in the API line, and will have to be replaced with one that has the appropriate number of licences. In the example of Alex Wongs own licence file, he has 12 Named Users.
Member for
22 years 8 monthsRE: Integration API - P3e
Chris
Make sure your license file have the following
// Project Management NU(12), CU(0), No Expiration Date
// Portfolio Analysis NU(12), CU(0), No Expiration Date
// Timesheets NU(0), CU(0), No Expiration Date
// myPrimavera Portfolios NU(12), CU(0), No Expiration Date
// myPrimavera Projects NU(12), CU(0), No Expiration Date
// myPrimavera Resources NU(12), CU(0), No Expiration Date
// Methodology Management NU(12), CU(0), Version: HEAVY, No Expiration Date
// Contractor NU(0), CU(0), No Expiration Date
// ContractorMaxDomains(+), MaxTasksPerDomain(+)
// Integration API NU(12), CU(0), No Expiration Date
Then you should be OK
Alex
Member for
20 years 5 monthsRE: Integration API - P3e
It looks like the API is available on the Primavera website.
My mob seems to have it already, so will try to get through the IT maze and install.
Then will have to start to learn a bit of Java. Thanks for the heads up.
Member for
20 years 5 monthsRE: Integration API - P3e
It looks like the API is available on the Primavera website.
My mob seems to have it already, so will try to get through the IT maze and install.
Then will have to start to learn a bit of Java. Thanks for the heads up.
Member for
19 years 3 monthsRE: Integration API - P3e
We may be talking about two different things. Ive referred to the API and its capabilities. If someone (and I know Primavera Australia is one) supplies software that makes integration easier, then that s/w would be at a cost. When Primavera is integrated with any other system, using the API, then someone has to do the work. (Even though all the "hooks" are there, and the data structure is well documented.) You may chose to do that yourselves, or contract it out. Or you may take advantage of someone else having already some or even all of that work. Perhaps that is what they are offering, you need to ask them.
Member for
22 years 8 monthsRE: Integration API - P3e
Dear All,
Are you sure API is free??
Because our dealer (Primavera Australia) is asking for A$25,000 for the use of it
Alex
Member for
21 yearsRE: Integration API - P3e
Chris,
I/We have lots of experience of the SDK and the API. As a company we build interfaces between work management systems, such as SAP and Maximo, to Primavera.
If you are an Excel guru who wants a cute single-user interface to Primvera the SDK is tolerable. If you want an industrial-strength multi-user interface that moves LOTS of data, the SDK is your worst nightmare.
The API is hard to use. You have to code in Java which is a special form of torture for us over 50s. It works. Code you create migrates from one version of Primavera to the next. DO NOT use the SDK for a "corporate" solution.
Member for
19 years 3 monthsRE: Integration API - P3e
Chris, even if there are no responses from API users in this forum , the API is certainly being used. Although the majority of users will have no need for it, there are many who do, and are doing. It is also used by Primavera partners who integrate their software with Primavera, including several who offer integration software to systems such as SAP.
The API is well documented, but someone has to do some programming.
Member for
20 years 5 monthsRE: Integration API - P3e
Sound like API is not being used. Sound like SDK might be the way.
Could not see how to export P3e Notebook Topics in Excel - can do it with the other Activity fields. Primavera (bless em) indicates that this may be an addon for the future!. Is there another way to get to Excel.
Looking at the Notebook Topic reports in HTML - seem to loose the formating on reporting.
Thanks for thetip.
Member for
19 years 3 monthsRE: Integration API - P3e
Neither the original API (ODBC, but observing the business rules) nor the newer one (XML) are charged for at present. They are both "delivered" on the CDs, but the XML API (on its own CD) is only useable after you have asked for it. It is not needed by most users, and is not initially included in your licence file. That is done on request, and requires the licence file to be amended.
Member for
22 years 8 monthsRE: Integration API - P3e
Hi
API - We we used API for integration. However, it have a cost. I believe Primavera Australia is selling the API license for approx A$20k+
Worth it or not... you have to justisfy it. I suggest you use SDK instead its free.
Secondly, Reporting with P3e ... yes P3e is rather limited.
Exporting using its existing export function should give you a very good output that can then create in Excel.
HTH
Alex