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.
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.
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.
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.
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.
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.
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
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.
- Don't see your idea?