UPDATE: We are applying a patch to address this Business Objects issue, which will be implemented in both the Training and Production Environments. These environments will be unavailable during the following patch periods:
- Training Environment - November 19th, 8:00 AM to 12:00 PM
- Production Environment - November 20th, 8:00 AM to 12:00 PM
If users experience any issues please follow your county process for reporting issues or you may contact the IBM Boulder Help Desk at 1-800-428-8268.
_____________________________________________________________________________
An issue has been discovered with the current version of Business Objects used with the CWS/CMS application.
Issue Description:
Whenever a numeric field, such as government entity code, is used as a condition in a data provider (query), the query will run correctly the first time. Whenever the data provider is edited, the system will return a type mismatch error and require the user to remove and re-add the condition. The query will then run, as long as it is not edited again.
This only appears to be an issue with numeric fields; character fields, such as Client Name, do not experience this issue. Once the query is run, it operates normally as long as the user does not go back and edit the data provider. The user can refresh the data and save, as well as edit the report formatting, without issue.
Issue Resolution:
A patch level update will be required to resolve the issue. The CWDS Office and IBM are evaluating the next Business Objects patch to determine if it will resolve the issue, without generating any new issues. There is currently no estimated time of when the patch will be implemented. Additional updates will be sent out as new information is received.
Workaround:
When Business Objects informs the user of a type mismatch error after a numeric field is used as a condition in a data provider, and the data provider is edited, then the user must remove and re-enter the condition. The query will run, without issue, as long as the data provider is not edited again.
Action Required
Until the issue is corrected with the appropriate patch update, users will need to perform the workaround listed above, by removing and re-entering the condition when they receive a type mismatch error message.