If you’ve created a workflow in SharePoint Designer and an email action appears to be configured correctly, but emails aren’t being sent to some individuals in the To: line, you may need to turn the email being used into a workflow variable and use that instead of direct addition to the To: line of the email step.
This often happens for group email inboxes or external recipients that aren’t just a “normal user.” If there is a mix of recipients, some may receive the message but the troublesome addresses don’t even appear in the To: line, as if they’re removed before sending.
Despite your regional settings being correct, all-day events for some reason are using UTC time when they’re stored and are likely showing as the wrong day in content search web parts and similar web parts.
Though they look correct as an individual item or on a calendar, the way they’re stored doesn’t acknowledge your regional settings and, when pulled through a search web part, render in UTC as beginning 6 (or other) hours earlier than they actually do.
For example, I have a content search web part that pulls all events in our organization and show’s “today’s events.” If there’s an all day event, it shows as starting 6:00 PM the day prior to its actual day.
I could not find a straightforward solution to fix all affected events. And my solution is not ideal, but it accomplishes a need. You could instead explore the possibility of creating a calculated column that adds hours to fix the alignment. But please share if you’ve encountered the same issue and have resolved it a better way.
There are three possible causes I’m aware of that you should check if you receive this message:
Central admin settings not configured properly
Site collection settings not configured properly
You’re using a Project Web App (PWA) site template and can only fix this on SharePoint Server
I’ll cover the solutions for each in the same order:
Go to central admin –> manage web applications
Select the web app on which you received the error and select “SharePoint Designer” from the general settings drop-down. Make sure the first box is checked and click “OK.”
Site collection settings
Go to site settings –> SharePoint Designer Settings (under Site Collection Administration)
Make sure “Enable SharePoint Designer” is checked and click OK
Project web app template issue
Log in to a SharePoint server and go to C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\TEMPLATE\SiteTemplates\PWA\XML
Open the ONET XML file in a text editor like NotePad
Search for “webdesign” (Ctrl+F to open search) and delete the following property:
Perform an IIS reset (run SharePoint management shell as administrator)
You may need to repeat these steps on multiple servers if you have multiple web front end servers. You can just copy the ONET file and overwrite the same file on the other servers in the same location. Don’t forget to do an IIS reset afterward on each.
Close and re-open your Project Web App site in SharePoint Designer and you should now be able to edit as you do with other sites.
I recently developed the above solution for a project requiring attachments at multiple points throughout the form. Originally I considered just placing a static “attachment button” in multiple places, but I came up with this and liked it better.
So if you also have long forms for your SharePoint lists, and you would like an easier way for end users to add attachments to list items, ditch the out-of-the-box ribbon menu attachment button and try this “floating attachment box” solution instead.
When you create a custom new item form in SharePoint Designer, you get a bonus set of “Save” and “Cancel” buttons automatically generated. One set at the top, and one set at the bottom (as generally seen on default forms).
Chances are if you’ve created a custom new item form, you had other intentions for the space now taken by duplicate buttons. Here’s how to get rid of the spare buttons and get back to designing and tweaking your custom new item form.
The aspx page that holds the content of the pop-up
The script that loads the aspx page in a modal dialog upon page load
Save this .aspx page to your “Site Pages” directory.
Copy and paste the following into a new .aspx page in your Site Pages or Pages (Settings wheel –> Site Contents –> Site Pages or Pages) directory:
We will be performing routine maintenance on SharePoint Librarian Monday morning from 4 am – 5 am. There may be a brief disruption for users online during that time. The maintenance window is scheduled for 1 hour.
Modify the content in the aspx page beneath the modal-content div and above the input tag to include your own images, formatting and message text.
Update the script to include the URL of your newly saved aspx page and a title for the pop-up window (optional).
Add a content editor web part to the page on which you’d like the pop-up.
Add web part
Edit web part
Save page/stop editing
I frequently reference two resources linked at the bottom of this post that speak to the features unique to 2010 and 2013 workflows. Unfortunately, once you pick which workflow platform you’ll be building upon you can’t switch. So it’s important to use these lists in your evaluation phase to make sure you’ll be picking the right platform for the job. Keep in mind, you can always start a 2010 workflow from within a 2013 workflow.
Perhaps one of the most useful automated processes out there is the ability to do approval processes. We fortunately have two tools on-prem or online that allows us to perform this action. Microsoft Flow offers some incredible connectivity between services (like approve a Tweet and post it, approve something from Google Docs and have it moved to SharePoint, etc.), but the approval process itself is very simple at this point and doesn’t offer some of the more robust features and customization options we get in SharePoint Designer 2013 approval processes.
I also will use both tools in the same business process occasionally, because they both have unique strengths.
But which do you use for approvals?
The quick answer to the question is: Use Flow for simple approvals, or approvals that involve multiple sites or external services. Use SPD for more complicated processes and customization options for approvals that involve a single site.
Below on the left are two traditional, out-of-the-box solutions for showing Today’s events in SharePoint. Notice how both take up a lot of extra space repeating today’s date (which we don’t need to see at all in a web part called “Today’s Events”) or showing gray space where there are no events. Soak that in – prime real estate on your home page goes to non-existent events. These also may require overlays and other manual labor processes that need adjusted every time a calendar is added or removed.
But on the right is what you could have. It uses search instead and displays events from all calendars a user has access to in one place. It shows only the necessary information on the home page and links to full details. And with a little CSS included in this post, it can look polished and themed. Imagine all you could do with that saved space on your home page…