I met my now husband at the Ignite 2015 Conference in Chicago. We shared a table at lunch with some other SharePoint junkies. He was married to someone else at the time so he went straight to the Friends Zone. We stayed in touch over social media asking each other for advice and tips on our respective SharePoint journies.
Flashforward to 2017 and SharePoint Saturday Twin Cities. He was a speaker from Portland, OR. I was an organizer from the Twin Cities. I offered to let him stay in the guest room for the event. We spent all of our waking time together.
He then flew out for a visit for Thanksgiving and met the family.
Again for Christmas.
I flew to Portland, OR for Valentine’s day.
By the end of May 2018, we were moving in together. Now we talk SharePoint, Teams and OneDrive all the time.
We decided to get married in May of 2021 but were thwarted by Covid-19. Pushed the wedding out a year to May 22, 2022.
It was worth the wait.
Thank you Microsoft to bringing two SharePoint junkies together in technology and in love.
Hey Tamara, Why can’t I delete the Calendar view I created in my SharePoint Online list? To delete any other view all I need to do is select Edit current view from the view drop-down and hit the delete button on the next screen. I don’t get that option when I try to edit the Calendar view. HELP!
Whew! That sounds frustrating. You are right in that the delete option is not available from the Edit current view selection. The Edit the current view option for the Calendar view looks like this.
Not a delete button in sight.
You can still delete the Calendar view the old-fashioned way.
Go to the list with the Calendar view.
Click on the cog in the upper right corner.
Select List settings.
On the List settings page, scroll down to the bottom where the views are listed.
Click on your Calendar view.
Now you will see the Delete button. Click the Delete button and the view is deleted.
Remember, deleted views do NOT go into the Recycle bin.
Ran into an issue the other day. A user was getting an error message when he tried to upload some Visio diagrams.
The strange thing was some of the Visio diagrams uploaded to the SharePoint Online site without any issues.
After searching the internet for the error message I ran across Vaikun Rajanihanth’s post from 2012 Invalid lookup value. The author correctly identifies the issue as the file was down loaded from another SharePoint site before the user tried to upload it to the current SharePoint site. The file still maintained the metadata from the first SharePoint site which caused the conflict while uploading the file to its new SharePoint location. The author details how to resolve the issue for a Word file, but the solution could not be applied to the Visio diagram because “Check for Issues” does not appear in the Info or Backstage view of the Visio file.
To remove the prior SharePoint metadata from the Visio file take the following steps…
Right click on the file name and select Properties from the drop-down menu.
In the Properties widow, click the Custom tab.
If there are no values in the Properties field, this is not the fix you need.
If you do see values in the Properties field, you are on the right path.
To remove the Properties, select the first Property and then click Remove.
Repeat this process until all Properties are removed.
You may now upload the file to your new SharePoint location without any issues.
Everyone is excited about their new Fantasy Football Teams and Leagues here in the United States. A lot of deliberation and planning go into selecting members of your team. Hours even days are spent pouring over players’ stats and skills before making the final choices.
What about our Fantasy SharePoint Teams? Imagine if you could build your dream team from the ground up.
What stats and skills would you pull onto the team?
Would you define roles and the skills needed to fulfill those roles OR would you define the skills and then define the roles based on the people with the various skills?
Would those skills be different if it was SharePoint Online, On Premises or Hybrid?
Would personality traits enter into the equation? If so what would they be?
Here’s a couple I think are needed regardless if you go old fashioned roles based or skills based.
Know and understand the tools available in the browser to prevent over development. Exam 77-419
Information Architecture / Library Science background
Search Engine Optimization
Keyword Query Language
Understand how SharePoint interacts with other Office Applications.
Create Search Results templates for SharePoint 2013
Know and understand SharePoint Designer Workflows, …
Can work in one or more of the following languages:
Understand and can make use of the client-side object model and REST APIs.
Just like everything else at the Microsoft SharePoint Conference 2014 (SPC14), SharePoint Social is being pushed into Heaven or Hell depending on your point of view. In fact it’s being pushed so hard it got pushed right out SharePoint and into Yammer and new apps.
Basically we are talking about no updates or enhancements to on-premises SharePoint Social.
Take a look at some of the new apps that make this loss more palatable:
Office Graph – Not just an org chart. Office Graph shows how you are working with people in the organization. Meetings you’ve both attended, documents you’ve worked on together and discussions you’ve shared are all incorporated into the relationship model. Office Graph serves up your connections instead of you having to search for your connections.
Oslo (codename) – I hate to say it, but it makes me think of Pinterest for Business. With so much information out there users are depending on images, context and search to find what they need to get the job done. Oslo takes care of the search and presents the information in a graphical format. Think of it as dynamic personal navigation.
Yammer Group Experience – You’ll need O365 for this one. When you create a group anywhere in O365 you will get a group inbox, discussion, Outlook web apps calendar and a SharePoint document library. That’s a lot of Office Apps seamlessly integrated to get the job done.
What does this mean for you?
Start considering a hybrid solution. Remember your organization’s Yammer environment can be locked down as tight as you’d like, but it’s still in the Cloud.
If you started using SharePoint Social features, stick with what you’ve got, but start planning for a change.
Don’t panic. SharePoint Social isn’t going away…at least not today.
NEVER use the word Facebook to describe enterprise social.
“People will be able to connect instantaneously, just like Facebook.”
“Our employees will be able to have conversations regardless of time of day or location, just like Facebook.”
That F word drives fear of a productivity black hole into the hearts of the CEO, CIO, CFO and most others on the leadership team in your organization. Some of them may have already been on Facebook. Your leadership team is already aware that Facebook can easily suck an hour or two out of your day. That isn’t productive, unless your company specializes in videos of people doing stupid things or produces cute pictures of cats doing stupid things.
If you want to sell enterprise social to the CEO, CIO, CFO or anyone else for that matter, show them how it will save time.
Do contracts take forever to review because you are doing it through email? How much turnaround time could be saved by having the discussion all in one place? Posting links to similar contracts within the conversation? Not only will it shorten the turnaround time for contracts, it will free up your sales team’s time to build more relationships with your clients.
Documents aren’t the only thing in an organization that need to be managed to mitigate risk and increase employee efficiencies. Videos, meeting recordings, blog posts, microblogs and activity feeds are all part of your enterprise content.
These frequently missed file types have now earned a place in your file plan and retention policies.
When a judge want to see all the information pertaining to a case, he or she isn’t interested in the easy to find documents, he or she wants all the INFORMATION your organization has retained regarding the issue at hand.
“Sorry, we don’t have a way to get that information to you” is not a viable excuse.
Writing a check for huge fines doesn’t make anyone happy.
My favorite quote from the KnowlegeLake User Conference on March 2nd, 2014 was from Pamela Doyle, Director or Fujitsu Computer Products of America, “Not managing your content is like driving a car 85 miles per hour in a school zone because you can pay the ticket. Obviously you haven’t considered any of the other possible ramifications”
Social is neat, Social is cool, Social is shiny, and it isn’t worth a darn unless it solves a business problem.
There are some organizations that install SharePoint Social features or Yammer because it’s the hip new thing. No training, no leadership buy-in, no business problem to solve. These implementations will be ignored by your co-workers, scorned by legal and lamented by HR.
If you want to prevent a “Social Debacle” within your organization put your ear to the ground. Listen for groups complaining about how hard it is to track things in email, find the most recent discussion on a document or project, and spending too much time in meetings discussing the same things over and over and over again.
Now you’ve found your business problem.
Talk to the group find out what they are doing and what they have tried to get the problem under control. Work with the group to create a place where these discussions can occur and be found later for review. Get the leader of the group or their boss involved early and make sure they participate in discussions and interactions.
If leadership isn’t using your Social Solution, no one will.
Make sure your Social Solution meets your users where they live; in email, on their mobile devices or in another location or piece of hardware. The business problem and how people will interact with your Social Solution is more important than the tool you choose.