Custom object not exposed to ODATA
Article ID: 215994
Updated On:
Products
Issue/Introduction
A user created a custom object and ran the jobs below in this order successfully.
- Load Data Warehouse - Full
- Load Data Warehouse Access Rights
- Refresh Data Warehouse Odata Model
The new custom object is in the Data Warehouse database, but it is not there when connecting to Odata.
Environment
Release : 15.9.1
Component : CA PPM SAAS ODATA
Cause
Refresh Grant database job was not running
The Refresh Grant database job creates and updates permissions and synonyms for these new database objects, now in the data warehouse. The automated Refresh Grant database job is scheduled to run every 2 hours. New custom objects are not visible as OData endpoints for reporting tools until the Refresh Grant job has completed and the Refresh Data Warehouse OData Model job has run after.
Resolution
Verify the Refresh Database job is running successfully.
- This is an automated job, not viewable in the UI so the DBA would be able to see if this job is running successfully
After it is confirmed running successfully, run the Refresh Data Warehouse OData Model
Additional Information
Feedback
