When Filtering on the Project LastUpdateDate Using P6 Web Services or P6 REST API the Results Are Incorrect
(Doc ID 2928262.1)
Last updated on FEBRUARY 16, 2023
Applies to:
Primavera P6 Enterprise Project Portfolio Management - Version 20.12.12.0 and laterPrimavera Web Services - Version 20.12.12.0 and later
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 20.12.12.0 and later
Information in this document applies to any platform.
Symptoms
When creating a request to load LastUpdateDate and also filter on LastUpdateDate the results do not match the filter.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a request to load the LastUpdateDate for a project.
https://uk1.p6.oraclecloud.com/<SERVICE NAME>/stage/p6ws/restapi/project?Fields=ObjectId,OverallProjectScore,LastUpdateDate
Response:
{
"LastUpdateDate": "2022-04-08T00:00:00",
"ObjectId": "12682",
"OverallProjectScore": "0"
}
2. Create a LastUpdateDate filter based off the results from the previous request.
https://uk1.p6.oraclecloud.com/<SERVICE NAME>/stage/p6ws/restapi/project?Fields=ObjectId,OverallProjectScore,LastUpdateDate&Filter=LastUpdateDate:gte:'2022-04-01'
3. Notice even though the results in Step #1 show a LastUpdateDate of 2022-04-08T00:00:00 the record is not returned when adding the filter of LastUpdateDate:gte:'2022-04-01'. This record should be returned since it meets the filter criteria.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |