CSOM API for Engagements in Project Server 2016 on premise is missing.
Please add CSOM API or allow another way to update engagements programmatically.
The Engagements CSOM API works well for Project Online but fails when attempteing the exact same code on 16 On Premise (minus the authentication off course).
The error seems to be coming from the server:
“Microsoft.SharePoint.Client.ServerException: Field or property “Engagements” does not exist.
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()"26 votes
Currently master Projects are not available via the CSOM API. The only way to retrieve Information about master projects is via OData.
There are scenarios were the possibility to obtain Information on master projects via CSOM is necessary:
Check if a user is allowed to see a master project or not
-3rd party system Integration
Update metadata of master Projects
Scheduling is a different topic and I would set up a new idea for that.22 votes
Add a flag (per site collection) so that users can choose whether HTML tags should remain in the ODATA feed
The removal of HTML tags in the ODATA feed has had severe implications for custom reports which relied on these tags in order to preserve the formatting entered into Enterprise Custom fields displayed on PDPs. Is it possible to provide a way to select which fields in the ODATA field have the HTML tags removed, or failing this, to allow the admin to decide at Site Collection or PWA instance level.17 votes
Provide support in the CSOM for querying and Approving Resource Assignments Programmatically. Resource Assignment approval will be very useful for assignments that break business rules, but not all assignments will. If approval for assignments was exposed to the CSOM, we could programmatically approve assignments that didn't break our rules, leaving the ones that do for a resource manager to approve.15 votes
Change the way Projects are saved and published so the process takes less time and less requests.14 votes
In most Office Desktop App you can customize the context menu. Please add this valuable feature also to Microsoft Project Desktop app:12 votes
CSOM currently is useless.... we have been doing an integration project with the Customer using CSOM data.
This CSOM is no where near PSI. Every time at every request you need to - Context.load and execute Query which adds on more time executing the code.
Please let me know if there is more efficient way to do this.
Please improve CSOM. Really Pathetic. and MS Support is useless. Really bad11 votes
Expand the reporting database to include key schedule data (e.g. predecessors, etc). These data are not readily accessible with PWA and could be used to create user-authored schedule audits.
-tracking the number of cross-project predecessors in an indirect measure of organizational collaboration, would help to market the value of PWA
-identifying schedules with complex predecessors (e.g. SF) and lead/lag is useful to building more robust project schedules10 votes
Support for the full suite of OData 4.0 functions in the project data endpoint.
Especially support for the function today. To allow excel (power BI) import of +/- 30 days of data.
And filter of expanded elements using the any/all keywords.10 votes
It is not possible to obtain a list of projects via CSOM and filter them beforehand using custom fields. This is quite hindering when working with a large list of projects.9 votes
In PSI, we can SummaryPublish a project to quickly update custom fields of a Project.
Using CSOM, only Full Publish option is available.
Please make summary publish option available.7 votes
Hi, it would be good to improve the deliverable/dependency data in order to create a map report.6 votes
When submitting a final timesheet within PWA, you are presented with a Comments window which will send a comment to your timesheet manager.
It would be extremely helpful if this Comment field was available via the timesheet OData feed, such as the timesheet line comment field currently is.
This would provide additional information to report on/track in relation to timesheets and resource comments.5 votes
It is unfortunate and wrong to limit the use of this feed to the max license type. Only users who can MODIFY the Project Server database should need a full project online license.
For reporting in read only mode, one should only need a lite license, or add a new inexpensive reporting only license.
Vote up and add additional justification here.5 votes
Please add the ability to reference the new Auto Project ID to a project server workflow in SharePoint designer. The field can be referenced through Odata in the Project table ProjectIdentifier field. However, it cannot be used on the workflow event string builder.4 votes
We are developing Project Professional Addin for Project Online and when we try to add OData service reference we get authentication error . For Fetching Data OData is better then CSOM.4 votes
Please, allow searching/indexing of project data. With that should then follow the ability to define crawled/managed properties, and then the ability to customize search results so we can build richer views of project data that also can incorporate relevant SharePoint data on the same page.3 votes
Offers remote event handlers for changes in Engagements (Create, Update or Delete).3 votes
Currently the ODATA API slightly changes the names for project and task custom fields to meet some API naming conventions. Although its almost possible to guess the real custom field names from the feed, it would be great to add a property to CustomFields CSOM API i.e ODATAInternalName, like we have InternalName to be used in CSOM itself.
Having Custom Field Creation Date would be also very helpful, as any new field is added to the end of the OData feed - this is how we could identify which column means which field.3 votes
Currently in OData's AssignmentTimephaseData has AssignmentModifiedDate which is identical with the Project's ModifiedDate in OData.
Even if you dont change the Assignments everytime you publish the project, AssignmentModified Date becomes the Project Modified Date . This is wrong, it should not modify the assignment's modified date for which i have made no changes in Project (Basically, OData does not have Delta)
I feel, What Project Online doing is Blindly Delete the Assignments from the OData Feed and Inserting them again.2 votes
- Don't see your idea?