prim28827:API exception: Local mode is not available. Please check your classpath.

February 15, 2014, 8:27 am

≫ Next: prim28912:Which ports need to be open for the API to be accessedthrough a firewall?

≪ Previous: prim28527:Can the API show spread data in Fiscal Years

Solution ID: prim28827

API exception: Local mode is not available. Please check your classpath.

Status: Reviewed

Version(s): 3.5.1, 4.0, 4.1, 5.0

Problem:	Although the API was installed in Local Mode, receive an Exception while attempting to login: com.primavera.integration.client.ClientException: Local mode is not available. Please check your classpath.
Problem:	Error received when trying to login to the Integration API: Fatal error: oracle/sql/BLOB.
Problem:	Error received when trying to login to the Integration API: java.lang.NoClassDefFoundError
Cause:	This error will occur if the API was installed in Local Mode, but the intgclient.jar file is included in the classpath instead of the intgserver.jar file. In order to run the API in Local Mode, the INTGSERVER.JAR file must be included in the classpath.
Fix:	To run the API in Local Mode, remove INTGCLIENT.JAR from the classpath and add INTGSERVER.JAR (as well as all other JAR files in the Primavera API\lib directory)

↧

prim28912:Which ports need to be open for the API to be accessedthrough a firewall?

February 15, 2014, 10:30 pm

≫ Next: prim29195:In what version didthe reporting APIbecome a feature?

≪ Previous: prim28827:API exception: Local mode is not available. Please check your classpath.

Solution ID: prim28912

Which ports need to be open for the API to be accessed through a firewall?

Status: Reviewed

Version(s): 4.0, 4.1, 5.0

From Primavera OCP

Problem:

Which ports need to be open for the API to be accessed through a firewall?

Problem:

Unable to access API through a firewall

Fix:

There are several ports which need to be opened for the API to be accessed through a firewall.

RMI Server port. This defaults to 9099, but can be changed in the API Administrator Tool (more about this later on in this document)

CompressionService port. This defaults to use any available (unspecified) port. This setting can be changed in the API Administrator Tool (more about this later on in this document)

SSLService This defaults to use any available (unspecified) port. This setting can be changed in the API Administrator Tool (more about this later on in this document)

StandardService This defaults to use any available (unspecified) port. This setting can be changed in the API Administrator Tool (more about this later on in this document)

HTTP port. This is usually 8080, but please check the settings on your web server and in the API Administrator Tool (more about this later on in this document)

It is not actually necessary to have all of CompressionService, SSLService and StandardService enabled as the RMI Server is able to function with just one of these services. However it’s possible to have a web application decide which service to use at run time, so all three are enabled by default. If, however, you know you’re only going to use one of these services, you can disable the other two and only open a port for the one you intend to use.

The API Administrator Tool can be accessed on a Windows System via Start, Programs, Primavera Integration API x.x, Primavera Administrator.

All of these settings are Configurations > Custom > {ConfigurationName} > IntegrationServer > RMI where {ConfigurationName} is the name of the configuration being used for the Primavera API.

The settings available are as follows:

RegistryPort – Port for the RMI Registry (default setting is 9099).

Enable
– Enables (true) or disables (false) the RMI server (default setting is true).

StandardServiceEnable – Enables (true) or disables (false) the Standard service mode (default setting is true).

StandardServicePort – Port to use for Standard service mode. A setting of 0 (default) means that any available port will be used. If the server will be accessed across a firewall, you must set this to a specific port.

CompressionServiceEnable – Enables (true) or disables (false) the Compression service mode (default setting is true).

CompressionServicePort – Port to use for Compression service mode. A setting of 0 (default) means that any available port will be used. If the server will be accessed across a firewall, you must set this to a specific port.

SSLServiceEnable – Enables (true) or disables (false) the SSL service mode (default setting is true).

SSLServicePort – Port to use for SSL service mode. A setting of 0 (default) means that any available port will be used. If the server will be accessed across a firewall, you must set this to a specific port.

The Primavera Administrator tool:

All this information can be found in the Programmers Reference HTML file which installs with the API. A copy of the Programmers Reference document for version 4.1 is attached below:

Programmers Reference document for version 4.1

↧

prim29195:In what version didthe reporting APIbecome a feature?

February 18, 2014, 12:23 am

≫ Next: prim29195:In what version didthe reporting APIbecome a feature?

≪ Previous: prim28912:Which ports need to be open for the API to be accessedthrough a firewall?

Solution ID: prim29195

In what version did the reporting API become a feature?

Status: Reviewed

Version(s): 8.0, 8.1

From Primavera OCP

Problem:

In what version did the reporting API become a feature?

Fix:

The reporting API was finalized in version 8.1.

Note: For more detailed information please refer to the Custom Reports documentation custom_reports.pdf (found in ‘\Primavera\docroot\help\en\doc’). See Chapter 3.1 ”API Functions” and Chapter 4 ”Security API Usage”.

See also prim33346 for a copy of the 8.1 custom_reports.pdf file.

↧

prim29195:In what version didthe reporting APIbecome a feature?

February 18, 2014, 12:23 am

≫ Next: prim29326:Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.

≪ Previous: prim29195:In what version didthe reporting APIbecome a feature?

Solution ID: prim29195

In what version did the reporting API become a feature?

Status: Reviewed

Version(s): 8.0, 8.1

From Primavera OCP

Problem:

In what version did the reporting API become a feature?

Fix:

The reporting API was finalized in version 8.1.

See also prim33346 for a copy of the 8.1 custom_reports.pdf file.

↧

prim29326:Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.

February 18, 2014, 11:08 pm

≫ Next: prim29326:Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.

≪ Previous: prim29195:In what version didthe reporting APIbecome a feature?

Solution ID: prim29326

Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.

Status: Reviewed

Version(s): 5.0

From Primavera OCP

Problem:	Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.
Problem:	Getting error: ‘PlannedStartDate: Assignment planned start date cannot be earlier than activity planned start date’ in the Integration API 5.0 and SDK 5.0
Cause:	Starting with version 5.0 of the Primavera Integration API and SDK, errors will be thrown regarding assignment start dates can not be earlier than activity start dates. The reason these errors are being thrown is that we are enforcing the business rule in Project Management where it would be impossible for a Resource to start working on an activity before the activity starts. Therefore, the resource assignment start date has to be the same or later than the activity start date.
Fix:	This is by design in the Integration API 5.0 and SDK 5.0. It is a business rule change in 5.0. Workaround: Get the activity’s actual start date and set it to a date prior to the resource assignment’s date that is being added.

↧

prim29326:Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.

February 18, 2014, 11:08 pm

≫ Next: prim29675:Is there the ability to create/update/delete more than 512 objects in one batch in the Integration API?

≪ Previous: prim29326:Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.

Solution ID: prim29326

Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.

Status: Reviewed

Version(s): 5.0

From Primavera OCP

Problem:	Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.
Problem:	Getting error: ‘PlannedStartDate: Assignment planned start date cannot be earlier than activity planned start date’ in the Integration API 5.0 and SDK 5.0
Cause:	Starting with version 5.0 of the Primavera Integration API and SDK, errors will be thrown regarding assignment start dates can not be earlier than activity start dates. The reason these errors are being thrown is that we are enforcing the business rule in Project Management where it would be impossible for a Resource to start working on an activity before the activity starts. Therefore, the resource assignment start date has to be the same or later than the activity start date.
Fix:	This is by design in the Integration API 5.0 and SDK 5.0. It is a business rule change in 5.0. Workaround: Get the activity’s actual start date and set it to a date prior to the resource assignment’s date that is being added.

↧

prim29675:Is there the ability to create/update/delete more than 512 objects in one batch in the Integration API?

February 24, 2014, 12:19 pm

≫ Next: prim29698:Error: Unable to resolve privileged username and password

≪ Previous: prim29326:Unable to assign a resource assignment prior to its activity’s actual start date in the Integration API 5.0 and SDK 5.0.

Solution ID: prim29675

Is there the ability to create/update/delete more than 512 objects in one batch in the Integration API?

Status: Reviewed

Version(s): 4.0, 4.1, 5.0

From Primavera OCP

Problem:	Is there the ability to create/update/delete more than 512 objects in one batch in the Integration API?
Problem:	Does the setBusinessObjectBatchSize(int iBatchSize) method in the Integration API affect how many objects can be created/updated/deleted?
Problem:	What is the default number of objects that can be loaded in one batch?
Problem:	What is the max number of objects that can be loaded in one batch?
Problem:	Getting error: “You cannot create/update/delete more than 512 objects in one batch” in the Integration API
Fix:	The Integration API uses a method called “Lazy loading”. You can load up to 4096 objects at once in batches. The default load size is 1024 and can be changed by using the setBusinessObjectBatchSize(int iBatchSize) of the Session object. The minimum value that can be set is 128. This is only used for loading objects. The Integration API will use the setting above to determine how many object to load in a time. For example: If you kept the default setting of 1024, and you call Project.loadAllActivities(Activity.getAllFields,null,null), the API will load the first 1024 activities. Once you get to the 1024th activity and then call next(), then the API will automatically load the next set of 1024 activities. Note: For this to work, you must be logged in until you are done working with all the activities since load calls are called when needed. This helps with performance. However, the Integration API is limited to the number of items that can be created/updated/deleted in one batch. The hard coded limit is 512 objects. There is no setting for changing this at this time.
Fix:	To increase this limit is an existing Enhancement Request. It will be considered for a future release

↧

prim29698:Error: Unable to resolve privileged username and password

February 24, 2014, 3:44 pm

≫ Next: prim29968:Can Past Period Actuals be updated through the SDK or API?

≪ Previous: prim29675:Is there the ability to create/update/delete more than 512 objects in one batch in the Integration API?

Solution ID: prim29698

Error: Unable to resolve privileged username and password

Status: Reviewed

Version(s): 4.0, 4.1, 5.0

From Primavera OCP

Problem:	Detail error message:- Error: Unable to resolve privileged username and password Failed Logon:com.jnetdirect.jsql.u: TCP/IP connection failed to host:java.net.ConnectException: Connection refused. connect url:jdbc:JSQLConnect://localhost:1433/database=PMDB
Problem:
Problem:	myPrimavera or API failed connect to the PMDB database during myPrimavera installation.
Problem:	Error while attempting to configure the API (or myPrimavera) to connect to local MSDE database using DBConfig utility (Database Configuration wizard): Error: Unable to resolve privileged username and password Failed Logon:com.jnetdirect.jsql.u: TCP/IP connection failed to host:java.net.ConnectException: Connection refused.
Cause:	The SQL Server Setup program and SQL Server Enterprise Manager grant unnecessary permissions to the SQL Server service startup account when the account is not a member of the Administrators Users group. -or- An unchecked buffer exists in an encryption function. A buffer overrun can occur as a result and can be used to either cause the SQL Server service to fail, or to cause code to run in the security context of the server that is running SQL Server. For more information about this problem, please refer to the following URL http://support.microsoft.com/kb/322853/en-us
Fix:	Install the SQL Server 2000 Security Tools http://www.microsoft.com/downloads/details.aspx?FamilyID=9552d43b-04eb-4af9-9e24-6cde4d933600&displaylang=en
Fix:	Upgrade SQL Server 2000 to Service Pack 3 http://www.microsoft.com/technet/prodtechnol/sql/2000/downloads/servicepacks/sp3.mspx

↧

prim29968:Can Past Period Actuals be updated through the SDK or API?

February 26, 2014, 3:31 am

≫ Next: prim30135:How to tell which version and service packof the Integration API is installed?

≪ Previous: prim29698:Error: Unable to resolve privileged username and password

Solution ID: prim29968

Can Past Period Actuals be updated through the SDK or API?

Status: Reviewed

Version(s): 4.0, 4.1, 5.0

From Primavera OCP

Problem:

Can Past Period Actuals be updated using SDK?

Problem:

How to view Past Period Actuals using the SDK or API?

Fix:

Past Period Actual data can be viewed using the SDK or the API.

- Using the SDK, Past Period Actuals can be viewed in the SPREADS tables, as well as the finDates, taskfin, and taskrsrcfin tables

- Using the API, Past Period Actuals can be viewed in the SPREAD classes.

- Using the API, Past Period Actuals can be updated using the ActivityPeriodActual Classes.

However, Past Period actual figures cannot be updated using the SDK. The SPREAD tables are read-only.

↧

prim30135:How to tell which version and service packof the Integration API is installed?

February 27, 2014, 3:14 am

≫ Next: prim30135:How to tell which version and service packof the Integration API is installed?

≪ Previous: prim29968:Can Past Period Actuals be updated through the SDK or API?

Solution ID: prim30135

How to tell which version and service pack of the Integration API is installed?

Status: Reviewed

Version(s): 3.5.1, 4.0, 4.1, 5.0, 6.0

From Primavera OCP

Problem:

How to tell which version and service pack of the Integration API is installed?

Problem:

How to tell which version of the Integration API I am currently using?

Fix:

To check which version and service pack of the API is installed, either:

– without logging into the API, check the Modified Date of either the intgserver.jar file (for Local Mode) or intgclient.jar file (for Remote mode)

– once logged into the API, call getFullVersion() from VersionInfo:

System.out.println(VersionInfo.getFullVersion());

The Modified Date and/or Full Version correspond to the API version & Service Pack as follows:

APIVersion	Intgserver.jar \ Intgclient.jar Modified Date	VersionInfo.getFullVersion()
3.5.1	11/04/03	3.5.1.0
3.5.1 SP 1	03/23/04	3.5.1.2
3.5.1 SP 2	04/09/04	3.5.1.2
3.5.1 SP 3	06/02/04	3.5.1.3
3.5.1 SP 4	07/16/04	3.5.1.4
3.5.1 SP 5	10/18/04	3.5.1.5
3.5.1 SP 6	11/01/04	3.5.1.6
3.5.1 SP 7	12/02/04	3.5.1.7
3.5.1 SP 8	02/17/05	3.5.1.8
4.0	02/17/04	4.0.0.0
4.1	06/11/04	4.1.0.0
4.1 SP 1	10/06/04	4.1.0.1
4.1 SP 2	03/31/05	4.1.0.2
4.1 SP 3	08/17/05	4.1.0.3
4.1 SP 4	09/20/05	4.1.0.4
4.1 SP 5	08/29/06	4.1.0.5
5.0	07/20/05	5.0.0.0
5.0 SP 1	09/14/05	5.0.0.1
5.0 SP 2	03/01/06	5.0.0.2
5.0 SP 3	08/31/06	5.0.0.3
5.0 SP 4	11/27/06	5.0.0.4
5.0 SP 5	07/23/07	5.0.0.5
5.0 SP 6	11/26/07	5.0.0.6
5.0 SP 7	03/10/08	5.0.0.7
6.0	06/22/07	6.0.0.0
6.0 SP1	09/13/07	6.0.0.1
6.1	11/21/07	6.1.0.0
6.1 SP 1	02/06/08	6.1.0.1
6.1 SP 2	04/16/08	6.1.0.2

↧

prim30135:How to tell which version and service packof the Integration API is installed?

February 27, 2014, 3:14 am

≫ Next: prim35579:Sample Code: How to remove a resource assignment through the SDK?

≪ Previous: prim30135:How to tell which version and service packof the Integration API is installed?

Solution ID: prim30135

How to tell which version and service pack of the Integration API is installed?

Status: Reviewed

Version(s): 3.5.1, 4.0, 4.1, 5.0, 6.0

From Primavera OCP

Problem:

How to tell which version and service pack of the Integration API is installed?

Problem:

How to tell which version of the Integration API I am currently using?

Fix:

To check which version and service pack of the API is installed, either:

– without logging into the API, check the Modified Date of either the intgserver.jar file (for Local Mode) or intgclient.jar file (for Remote mode)

– once logged into the API, call getFullVersion() from VersionInfo:

System.out.println(VersionInfo.getFullVersion());

The Modified Date and/or Full Version correspond to the API version & Service Pack as follows:

APIVersion	Intgserver.jar \ Intgclient.jar Modified Date	VersionInfo.getFullVersion()
3.5.1	11/04/03	3.5.1.0
3.5.1 SP 1	03/23/04	3.5.1.2
3.5.1 SP 2	04/09/04	3.5.1.2
3.5.1 SP 3	06/02/04	3.5.1.3
3.5.1 SP 4	07/16/04	3.5.1.4
3.5.1 SP 5	10/18/04	3.5.1.5
3.5.1 SP 6	11/01/04	3.5.1.6
3.5.1 SP 7	12/02/04	3.5.1.7
3.5.1 SP 8	02/17/05	3.5.1.8
4.0	02/17/04	4.0.0.0
4.1	06/11/04	4.1.0.0
4.1 SP 1	10/06/04	4.1.0.1
4.1 SP 2	03/31/05	4.1.0.2
4.1 SP 3	08/17/05	4.1.0.3
4.1 SP 4	09/20/05	4.1.0.4
4.1 SP 5	08/29/06	4.1.0.5
5.0	07/20/05	5.0.0.0
5.0 SP 1	09/14/05	5.0.0.1
5.0 SP 2	03/01/06	5.0.0.2
5.0 SP 3	08/31/06	5.0.0.3
5.0 SP 4	11/27/06	5.0.0.4
5.0 SP 5	07/23/07	5.0.0.5
5.0 SP 6	11/26/07	5.0.0.6
5.0 SP 7	03/10/08	5.0.0.7
6.0	06/22/07	6.0.0.0
6.0 SP1	09/13/07	6.0.0.1
6.1	11/21/07	6.1.0.0
6.1 SP 1	02/06/08	6.1.0.1
6.1 SP 2	04/16/08	6.1.0.2

↧

prim35579:Sample Code: How to remove a resource assignment through the SDK?

July 6, 2014, 10:45 am

≫ Next: prim35633:Getting error: “File or assembly name pvapi, or one of its dependencies, was not found.” when using the API sample Excel application

≪ Previous: prim30135:How to tell which version and service packof the Integration API is installed?

Solution ID: prim35579

Sample Code: How to remove a resource assignment through the SDK?

Status: Reviewed

Version(s): 4.0, 4.1, 5.0

From Primavera OCP

Problem:

Sample Code: How to remove a resource assignment through the SDK?

Fix:

1. Open SDK tables.

2. Set the Scope and Access level for the Project that this activity and resource assignment are a member of.
ex.
Update OAUSER_Project SET scope_level = 7, access_level = 1 WHERE OAUSER_Project.proj_id = 1015;

(where 1015 is the project id)

3. Go to the TASKRSRC table and find the taskrsrc_id of the resource assignment to be deleted

4. Create a new query to delete this
ex.
DELETE OAUSER_TASKRSRC.taskrsrc_id FROM OAUSER.TASKRSRC WHERE OAUSER_TASKRSRC.taskrsrc_id = 105138;
(where 105138 is the taskrsrc_id of the assignment to be deleted)

Then run this query this should delete this assignment
(Test this code out on a sample or test project first)
(Also it is recommended to have a backup of your database before running any deletes through the SDK or API)

↧

prim35633:Getting error: “File or assembly name pvapi, or one of its dependencies, was not found.” when using the API sample Excel application

July 7, 2014, 1:14 am

≫ Next: prim35667:”Error received when trying to install Primavera 5.0 Integration API on Windows 2003 server:”

≪ Previous: prim35579:Sample Code: How to remove a resource assignment through the SDK?

Solution ID: prim35633

Getting error: "File or assembly name pvapi, or one of its dependencies, was not found." when using the API sample Excel application

Status: Reviewed

Version(s): 8.5

From Primavera OCP

Fact:	Office 2003
Problem:	Getting error: “File or assembly name pvapi, or one of its dependencies, was not found.” when using the API sample Excel application
Cause:	There was a step left out of the instructions in the Primavera Application Programming Interface (API) user guide section 11.2 for setting up the sample Excel application.
Fix:	An earlier version of Excel is being used. This add-in only works with Excel 2003.
Fix:	In order to use the sample Excel application with Excel 2003, you have to install an Office 2003 update. To do this, do the following: Go to this link and install this Update for Office 2003 to make it work with .NET Framework 2.0: http://www.microsoft.com/downloads/details.aspx?FamilyID=1b0bfb35-c252-43cc-8a2a-6a64d6ac4670&DisplayLang=en. Note: The full instructions for setting up the sample excel application can be found in the readme.txt file in the ‘pvapi\client\dotnet\excel-sample’ folder.

↧

prim35667:”Error received when trying to install Primavera 5.0 Integration API on Windows 2003 server:”

July 7, 2014, 7:33 am

≫ Next: prim35739:java.sql.SQLException: connection has been recycled

≪ Previous: prim35633:Getting error: “File or assembly name pvapi, or one of its dependencies, was not found.” when using the API sample Excel application

Solution ID: prim35667

"Error received when trying to install Primavera 5.0 Integration API on Windows 2003 server:"

Status: Reviewed

Version(s): 5.0

From Primavera OCP

Fact:	Windows 2003 Server
Problem:	Error received when trying to install Primavera 5.0 Integration API on Windows 2003 server: “The instruction at “0x#######” referenced memory at “0x#######”. The memory could not be “written”. Click OK to terminate the program.”
Cause:	To run the Integration API installer you must have a JRE installed. To tell if a JRE already exists on the machine, open up a Command prompt and type “C:>java -version”. The results will look something like this : You can also check the Add/Remove Programs control panel to see if there is a JRE installed on the machine.
Fix:	If there is no JRE installed, you can install one from the Primavera 5.0 Documentation CD, DOC CD:\Documentation\JRE\JRE1.4.2_07\windows\j2re-1_4_2_07-windows-i586-p.exe There is also a 1.5.0_01 JRE available on the CD in the JRE folder. WARNING : Installing the JRE may force a reboot of your machine. Once the JRE is installed, install the Integration API

↧

prim35739:java.sql.SQLException: connection has been recycled

July 7, 2014, 4:58 pm

≫ Next: prim35902:Primavera 8.5 Custom Reports guide (Reporting Views Manual)

≪ Previous: prim35667:”Error received when trying to install Primavera 5.0 Integration API on Windows 2003 server:”

Solution ID: prim35739

java.sql.SQLException: connection has been recycled

Status: Reviewed

Version(s): 4.1, 5.0

From Primavera OCP

Fact:

Integration API

Problem:

java.sql.SQLException: Connection has been recycled

Fix:

Increase the MaxLeaseDuration and LongRunningMaxLeaseDuration

Go into the Primavera Integration API Primavera Administrator (Run admin.cmd from the Integration API folder or go to Start, Programs, Primavera Integration API, Primavera Administrator). Expand the configuration and database folder. You will then see these options there.

↧

prim35902:Primavera 8.5 Custom Reports guide (Reporting Views Manual)

July 11, 2014, 1:51 pm

≫ Next: prim35909:How to add a field to the where clause with data type java.sql.Date (ie CreateDate or LastUpdateDate) when loading a business object into the BOIterator in API?

≪ Previous: prim35739:java.sql.SQLException: connection has been recycled

Solution ID: prim35902

Primavera 8.5 Custom Reports guide (Reporting Views Manual)

Status: Reviewed

Version(s): 8.5

From Primavera OCP

Problem:	Where is the Primavera 8.5 Custom Reports guide?
Problem:	Where can custom_reports.pdf be found?
Problem:	Where is the Reporting Views document (reporting_views_manual.pdf) in versions 8.1 and later?
Problem:	How to configure Actuate custom reports to use the Primavera Security API?
Problem:	Developing Custom Reports for Primavera 8.5.
Fix:	Please click the link below to download the Primavera Custom Reports guide for version 8.5: custom_reports.pdf This file can also be found in the following location: - On the server installed to the ‘\Primavera\docroot\help\en\doc’ folder. (This document was called “Reporting Views Manual” / reporting_views_manual.pdf in versions prior to 8.1.) Note: Chapter 3 lists the API functions available and Chapter 4 goes over configuring Actuate custom reports to use the Primavera Security API.

↧

prim35909:How to add a field to the where clause with data type java.sql.Date (ie CreateDate or LastUpdateDate) when loading a business object into the BOIterator in API?

July 13, 2014, 11:21 am

≫ Next: prim35911:Primavera 8.5 Client Services Descriptions guide for Primavera Web Services API

≪ Previous: prim35902:Primavera 8.5 Custom Reports guide (Reporting Views Manual)

Solution ID: prim35909

How to add a field to the where clause with data type java.sql.Date (ie CreateDate or LastUpdateDate) when loading a business object into the BOIterator in API?

Status: Reviewed

Version(s): 5.0

From Primavera OCP

Problem:	How to add a field to the where clause with data type java.sql.Date (ie CreateDate or LastUpdateDate) when loading a business object into the BOIterator in API?
Fix:	This issue is an existing Enhancement Request. It will be considered for a future release.
Fix:	As a workaround it’s possible to compose a string to hold the required Where clause values. For example the ‘condition’ string below will ensure Resource Assignments are loaded where the LastUpdateDate is later than a given date: - For SQL: Calendar lastUpdateDate = Calendar.getInstance(); String condition = “LastUpdateDate > ‘”; condition += lastUpdateDate.get( Calendar.YEAR ) + “-” + ( lastUpdateDate.get( Calendar.MONTH ) + 1 ) + “-” + lastUpdateDate.get( Calendar.DAY_OF_MONTH ) + ” “; condition += lastUpdateDate.get( Calendar.HOUR_OF_DAY ) + “:” + lastUpdateDate.get( Calendar.MINUTE ) + “:” + lastUpdateDate.get( Calendar.SECOND ) + “‘”; boi = elm.loadResourceAssignments( null, condition, null ); - For Oracle: Calendar lastUpdateDate = Calendar.getInstance(); String condition = “LastUpdateDate > “; condition += “to_date(‘”; condition += lastUpdateDate.get( Calendar.YEAR ) + “-” + ( lastUpdateDate.get( Calendar.MONTH ) + 1 ) + “-” + lastUpdateDate.get( Calendar.DAY_OF_MONTH ) + ” “; condition += lastUpdateDate.get( Calendar.HOUR_OF_DAY ) + “:” + lastUpdateDate.get( Calendar.MINUTE ) + “:” + lastUpdateDate.get( Calendar.SECOND ) + “‘”; condition += “, ‘YYYY-MM-DD HH24:MI:SS’)”; boi = elm.loadResourceAssignments( null, condition, null ); - Where ‘elm’ is an instance of the EmterpriseLoadManager and ‘boi’ an instance of a Business Object Iterator.
Fix:	The WhereClauseHelper class may also be used to construct a WhereClause with dates: SimpleDateFormat formatter = new SimpleDateFormat( “MM/dd/yyyy” ); Date date = formatter.parse( “03/03/2005″ ); String dateBegin = WhereClauseHelper.formatDate( date ); date = formatter.parse( “03/09/2005″ ); String dateEnd = WhereClauseHelper.formatDate( date ); String whereClause = “ActualStartDate between ” + dateBegin + ” and ” + dateEnd; BOIterator boi = project.loadAllActivities( new String[]{ “Id”, “Name” }, whereClause, “Name desc” );