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”.
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.
برای راه اندازی ویندوز 10 میشود با Any Disk کمک کنید3 votes
Closing as we only can handle English requests.
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.
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.
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.
Please stop changing the Design Methodology with every major Upgrade. Every major upgrade forces the developer/designer to learn a new way to redesign a custom look and feel. This makes upgrades painful and dreaded. Please allow for backwards compatibility for prior design work.2 votes
Thanks for your feedback! Your input has been noted and is taken into consideration for the future releases of SharePoint.
Microsoft messes with my interface and then requires me to download some thing and fix it. Thanks for nothing.1 vote
This is not unfortunately actionable for us as there are no actual details. Closing this as we can’t really do anything with given information.
I'm trying to create a network of sites collected under regional hub sites and in turn associate those regional hubs under a bigger hub site.1 vote
This is not supported. Site collections can be associated with hub sites, but you cannot associate hub site to hub site. In general, we would recommend using our community forums for these kinds of questions as this is not really a feature suggestion.
See for example http://aka.ms/sppnp-community.
What does ODSP stand for? Acronyms are vital, however only if they are explained in the footnote.
This comment is in regards to this artical: https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/multigeo-introduction1 vote
The referred article starts with following line – “The OneDrive and SharePoint Online (ODSP)”. ODSP means OneDrive and SharePoint.
We are happy to adjust the documentation as needed and feel free to add documentation suggestion feedback or even submit a pull request in GitHub for update suggestion.
pasting the code into visual studio does nothing. It says,"no schema selcted". Also, this is not a full definition. What values are allowed?
Make things work the way you straight up said they would.1 vote
Closing this as there’s no context of the request, so submission is unfortunately not actionable. If you have an issues with provided documentation, please report details using http://aka.ms/spdev-issues.
Also please provide following details, so that we can investigate and react on your feedback.
- What code are you referring to?
- Where is this code located?
- Where in the VS are you pasting the code?
- Are you following some tutorials or what are you trying to do?
- What is not a “full definition”?
- What are the values you are referring to?
- Which VS version you are using?
Thanks for your submission and additional details advance, so that we can make things work the way they would.
This sis an issue I am facing, not an idea. Adding the helloworld webpart does not work in Edge but works in Chrome.1 vote
Since this is an issue, not an idea, we would suggest submitting this from the http://aka.ms/spdev-issues. Please also include additional details on which sample you were using, what are the versions of your browser and also which operating system you are using.
And I wonder how to add new row to jquery datatable with data enter from right pane!
Can I do this?
For technical support, we would recommend using following channels as UserVoice is for new feature requests.
Closing this one as this is not a new feature request for SharePoint service / product.
Could you add a sample with angular routing in a webpart ? Because with every page that is loaded through routing , angular is not working
Could you add a sample with angular routing in a webpart on GIt (https://github.com/SharePoint/sp-dev-fx-webparts) ? Because with every page that is loaded through routing , angular is not working in my case1 vote
Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now from engineering side. We do understand that there is a need for different kind of samples for the community, but we are not prioritizing them through the UserVoice process, so closing this one from here.
This is not supported due to browser limitations. As this is not an enhancement capability for SharePoint and we cannot influence browser security settings, closing the item from here.
If I need to deploy Simple Hello world webpart using SPFx, I have to install 4-5 installables,
can it be done with autoinstallers/Wizards, and when developer create new project , automacally default files will be created in project.. I have new to SPFx,in case if it already in place please share the links.
When you deploy a web part to SPO, only item you need to deploy is the sppkg file to app catalog. When you create a new web part, only item you need to execute is the Yeoman generator for giving you the default starting point. Please see more details on the Getting started guidance at http:/aka.ms/spfx.
Installing node, gulp, yo etc. has to be only be done once per environment.
if SP pages allow to edit using C# or VB language it depends heavily on java and json why not MSFT own languages1 vote
You can create and manage modern pages in SharePoint using remote APIs which are also available through C# and VB. SharePoint does not use Java.
Sharepoint filtering not working in Chrome as of last week and the response is to that Sharepoint only optimized for IE
At the direction of your help staff we use Chrome as our main browser. As of last week, filtering is not working, and when I spoke with two different support from 365 they told me that Chrome will no longer be supported and that we need to switch to IE, which we continually have problems with...locking up constantly.1 vote
As this is missing actual details, we’ll need to close this. There are no details on what filtering this is actually referring to and how it’s not working properly.
Chrome is absolutely supported browser in SharePoint Online and there are no optimizations for IE. This is unfortunately false information which should be corrected.
On the supported browsers in SharePoint Online, please have a look on following article https://support.office.com/en-us/article/which-browsers-work-with-office-online-ad1303e0-a318-47aa-b409-d3a5eb44e452
We need a betherthan interface.1 vote
Closed due lack of details on the requested capability.
- Don't see your idea?