Categories and tags are the two default taxonomies that we use at the European SharePoint, Office 365 & Azure Community website. By design, all posts must be filed under at least one category. As you can imagine, ‘General’ is where we can list almost any topics that is not filed under the other subject headings.
However, some subjects are wide and broad in subject and need to be included in our blog, but don’t quite fit under the existing taxonomies. Hence the ‘General Category’. Content covered can vary from a .NET Runtime for AOT to a SharePoint Conference North America Keynote Summary, Pulse Survey or monthly top SharePoint, Office 365 & Azure resources.
This short article shows you how to create tab look in SharePoint Custom Lists When I went to http://www.w3schools.com/howto/howto_js_tabs.asp. I saw the tab I want but how am I going to put this in my Office 365 SharePoint. Create a SharePoint Custom List Open SharePoint Designer 2013 and point to the SharePoint site. Choose Lists… READ MORE
This blog gives you step by step details on how to set the document library webpart view to specific sub folder. OOB SharePoint online does not support view to show the sub folder of the document library. This can be achieved in 2 ways By changing the view page Query using the SharePoint Designer Java… READ MORE
Script that allows to get all the users for all the Site Collections in a SharePoint Online Tenant
Here’s the scenario: You have a picture library that stores employee photos. This might be the case if you’re not storing the photos in Active Directory yet perhaps. Now, HR comes to you and says that “we want to be sure that employees can’t set an alert, because then they would know if we remove a picture when an employee is terminated”. Hmmm I never thought about it in that way, you’re right
Using PowerShell, we’re going to walk through handling a Choice field in a list. Specifically, this is a calendar list using the Category field. This may come in handy if you want to automate changing the values from another data source that BCS can’t connect to, or is too much work to get it to connect. I always prefer using SharePoint’s features, but sometimes we need to stretch it to make it work.
The SharePoint platform has gone through some major changes over the past decade, from a loosely tied collection of disparate tools (Tahoe), to a limited product implementation (SPS2001, 2003, and 2007), to a dynamic and powerful platform (2010) — and even now it is evolving in response to the changing world of BYOD (bring your own device) and cloud-based infrastructures and services.
When working with customers one often hears the following complaint: “Wow, this SharePoint is sooo ugly…”. I personally think SharePoint 2010 has very nice nice and professional design, but since customer is always right, from time to time I need to make it look more pretty. For some customers the “fix” is very simple, just add some nice looking buttons on the home page and they will be very happy with this improvement.
Couple of things that your customer needs to be able to do:
Add/Remove buttons easily
Add icons to buttons
Rearrange buttons as web parts
Change layouts i.e. order buttons vertically vs. horizontally
The unveiling of our 2011 keynote speakers continues as we release two more fantastic and inspiring videos direct from Berlin, offering valuable insights and visions from our keynote presenters.
In a previous post I shared some thoughts regarding changes to authentication providers in SharePoint 2010. As I worked through the issue of removing Claims/FBA and reverting to NTLM I discovered a number of issues that manifested themselves in strange ways. The first problem I encountered was the inability for a Farm account to make changes to the Authentication Providers settings in Central Administration. The System Account couldn’t even view the dialog – each attempt resulted in a 403 error. This was bad news as a lot of things happen behind the scenes when changing authentication settings in this dialog – not the least of which is propagation of changes to all the web servers. This meant I would have to undo all of the Claims settings manually and repeat them on each server. Not my idea of a fun afternoon.
When you remove field from the Sharepoint list either from UI or programmatically you may encounter with the following exception (I faced with this problem when removed managed metadata field, but it can be also any type of field):
