Forum Discussion
API reporting data fields and limitations
Hello netmarcos ,
This wont be added to the Project Online Odata API. You could have a new Enterprise Custom fields in Project Online and programmatically write the baseline saved dates to those fields. I wrote a simple example many years ago for on-premises but the same concept will work for Project Online for baselines created in the Project Client. For baselines created in PWA, this approach wont work.
Paul
Hello netmarcos ,
This wont be added to the Project Online Odata API. You could have a new Enterprise Custom fields in Project Online and programmatically write the baseline saved dates to those fields. I wrote a simple example many years ago for on-premises but the same concept will work for Project Online for baselines created in the Project Client. For baselines created in PWA, this approach wont work.
Paul
- Messy but I guess effective. It would be an enormous challenge to get a client-side macro approved in our (Government) environment.
Curious though: for on premise installations, I would simply pull this data from draft.MSP_TASK_BASELINES_PUBLISHED_VIEW or Pub.MSP_TASK_BASELINES. I suppose those days are gone.Hello netmarcos ,
On premises it is not supported to query the pub schema with T-SQL, it is only supported to query the reporting schema (pjrep).
Paul
- I'll go sit in my corner. There are probably a lot of things that I have done that are not supported.
