Besides the lack of detailed documentation around the REST API, given its importance as a major entry point for apps, it needs to be treated with more respect as a service offering. It's currently being updated in CUs and on SharePoint online without any notification of the changes being made (such as the $metadata endpoint appearing - was it in the August 2013 CU for on-prem?). We either need it to be released in a non-breaking change model (URL versioning such as the Twilio model), or messaging needs to be improved so we know when things are going to be changed. Having a log of changes that have been made to date would be helpful, along with understanding what changes are currently in the queue. For example, I would LOVE to know if the end game for the _api endpoint is to finally be a first-class OData v3 endpoint sometime soon.
Besides the lack of detailed documentation around the REST API, given its importance as a major entry point for apps, it needs to be treated with more respect as a service offering. It's currently being updated in CUs and on SharePoint online without any notification of the changes being made (such as the $metadata endpoint appearing - was it in the August 2013 CU for on-prem?). We either need it to be released in a non-breaking change model (URL versioning such as the Twilio model), or messaging needs to be improved so we know when things are going to be…248 votes
We are actively working on the REST API and Graph API documentation improvements, but as this issue does not have clear explicit delivery criteria, we are closing it to ensure that it does not hide any other critical gap with more specific delivery details.
We are highly interested on improving the documentation and are absolutely open for suggestions, but also want to ensure that the votes are available for more concrete submissions.
Setting status as closed as we definitely are not declining this and are actively working on it, but would not consider it also as “done”.
The SharePoint Online Web Service doesn't support apponly token, please help support it, then we can call web service API which is not available in CSOM.
Thank you.3 votes
Closing as no response after requesting additional details.
I am using the UserProfile.BatchUpdate.API for like 2 years without any problem. I have accidentally noticed that the API is not working anymore. It is not important, if i trigger the sync job with one user or multiple in the JSON file or if i try to sync multiple attributes or one attribute, i am just getting an internal error like this one:
Job ID: 07bb3ef9-60a2-46d0-a467-396b9428abf5
Job State: Error
Error State: InternalError
Logged errors: Failed to import the custom properties due to an unexpected error.
Please fix the api!3 votes
As this is an issue report, we are closing it from UserVoice, which is targeted for new enhancements. We would recommend using following routes for any issue reporting:
- Premier Support – if possible
- Non-development support through tenant admin support channel at the tenant admin UIs
- Developer support through http;//aka.ms/spdev-issues
Sorry for the inconvenience.
There are issue in migrating the classic page to modern using .Net based SharePoint PnP Modernization framework.
I get below error. It is random, sometimes i get this error and sometime not. Tried 'Include(WelcomePage)'.Nothing works. Any suggestion please
The property or field 'WelcomePage' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested.3 votes
Thank you for your issue report. As this is not a new feature request, rather a bug report on existing capability, we will be closing this from UserVoice and would ask that it’s reported at the GitHub issue list around the modernization tooling – https://github.com/SharePoint/sp-dev-modernization/issues.
According to Microsoft documentation, "Prefix matching is also supported with phrases specified in property values, but you must use the wildcard operator (*) in the query, and it is supported only at the end of the phrase." This is extrememly limiting. Why can't the wild card be anywhere in the query? This functionality would be great.2 votes
As we don’t support SQL usage with SharePoint, this seems to be in a wrong UserVoice and closing the request.
Be able to get the history of changes of the record of a list in sharepoitn through ODATA, to be able to track custom fields in the lists.
from lists within sharepoint, or from project sites in project online.0 votes
Closed as a duplicate.
- Don't see your idea?