SP Designer Archives - Daniel Glenn

SharePoint Workflows are Dead (Almost)

Daniel — Mon, 20 Jul 2020 04:34:22 +0000

The end of support for “SharePoint 2010 workflows” in Microsoft 365 will be November 1st, 2020. The title of the blog post, Support update for SharePoint 2010 workflows in Microsoft 365, doesn't make it clear, but we are seeing the beginning of the end for SharePoint workflows in SharePoint Online. This is truly the end of SharePoint workflow. End of SharePoint Workflow It isn't a surprise that Microsoft is moving to not support native workflows in SharePoint. At Microsoft's Ignite conference in 2016, Microsoft announced that support for SharePoint Designer workflows (and InfoPath forms) in SharePoint Server (on-premises) would in time not be supported. The end of support date was stated to be until 2026. However, the key to those announcements and subsequent blog posts was that they were talking about the on-premises versions of SharePoint Server. There has never been a promise to support older versions of workflows in SharePoint Online for that period of time. There also has never been a timeline released when SharePoint workflows would stop being supported in SharePoint Online – until now. At time of publication, the older blog posts announcing the on-premises changes could not be located. What was assumed at the time, though, was that Microsoft would give ample amount of notice when existing workflows would be removed from SharePoint Online. SharePoint 2010 Workflows have been deprecated If you received this warning when you looked at your workflow page, then your tenant has already been affected. So what is actually being changed? Read on. What Exactly is Being Removed There is some confusion because the specific workflow engine being removed is being called “SharePoint 2010”. However, this isn't a signal of the version of SharePoint itself, but the version of the workflow engine. There are two different categories of workflows that are included in the retirement: 1) out of the box workflows that come with SharePoint and 2) workflows created using SharePoint Designer. Out of the Box Workflows There are several out of the box (OOTB) workflows that have been available to configure in document libraries and lists for many past versions of SharePoint. OOTB workflows are easily created and maintained within the SharePoint user interface (UI). These workflows include Approval, Collect Feedback, Collect Signatures, Disposition Approval, and Three-state. These workflows are used widely by power users, developers, and site users. They are configured easily in the UI and because they are OOTB, don't usually fail because of a step that has been configured incorrectly. 2010 Workflows Created with SharePoint Designer The other category of workflows that will be disabled are those created with SharePoint Designer (SPD). SPD is a free application that has been used by power users, administrators, and developers around the world to edit SharePoint pages, modify settings, and create powerful workflows. Both SharePoint Designer 2010 and SharePoint Designer 2013 versions can create 2010 workflows – the workflow author chooses what engine when they first create the workflow. When Will SharePoint Workflows be Disabled? As reported in the blog announcement, there are several dates to keep in mind. August 1st, 2020 – after August 1st, any new Microsoft 365 tenants will have 2010 workflows disabled. November 1st, 2020 – on November 1st, Microsoft will begin disabling all 2010 workflows on all sites. Also in November 2020, 2013 workflows will be disabled by default for any newly created Microsoft 365 tenants. Are 2013 Workflows Being Removed? If this is the end of SharePoint workflow, are 2013 workflows being removed too? Starting in November 2020, Microsoft will disable 2013 workflows by default for any newly created tenants. However, administrators will be able to turn it back on via PowerShell. Microsoft is not giving a timeframe for when 2013 workflows will be removed just like 2010 workflows. They will be ‘deprecated' in November 2020, which is the first step in saying they will be removed in the future. It is my opinion that if the process of 2010 workflows goes smoothly, then the 2013 workflows will not be far behind. So what do I mean by ‘smoothly'? My first requirement for this to be ‘smooth' is if customers don't complain too much. Some customers say less than 4 months notice is far too little time. This also comes during a global pandemic that has organization budgets stretched thin. There is a UserVoice created with over 1,000 votes and if you feel the notice of change is too short, you can vote there. My second requirement for this to be ‘smooth' is if removing the workflows is successfully performed and happens without causing issues for sites. What Do We Do Now? A good resource to help you get started in the process is Microsoft's support article SharePoint 2010 workflow retirement. The page lists how to identify your workflows, and says you should recreate the workflows in Power Automate. The first step will be to identify the workflows you have running on your sites using the SharePoint modernization scanner. Second, organizations need to identify which of the workflows in their environment are being used and should be recreated in Power Automate. This second step might take some time if you have been using SharePoint for many business processes in your environment. The third step is to then recreate the workflows in Power Automate. There are five points to go into this process. Working with the owners to recreate the workflow Incorporating any process improvements Identifying gaps in Power Automate functionality that might need more complex processes Testing Running a change management program to roll out the new workflows That could be a tremendous amount of work. You need to know if you can make progress during the 3.5 months you have before your workflows are disabled. Need Help? If you find that you need some help with any of the steps above to meet the deadline, make sure you contact me! Fill-out my contact form and let me help.

The post SharePoint Workflows are Dead (Almost) appeared first on Daniel Glenn.

Cincinnati SharePoint User Group – June 22nd

Daniel — Thu, 15 Jun 2017 16:48:37 +0000

On June 22nd 2017, I will again be speaking to the Cincinnati SharePoint User Group and this time around we will be discussing workflow. I will present the options for creating workflows in SharePoint and Office 365, as well as look at the process (and potential pitfalls) for upgrading your SharePoint Designer workflows to Microsoft Flow. Find details on the topic, as well as register on the Meetup page. [UPDATE] Thank you so much to everyone who came out tonight to the meeting – I had a great time and the group participation was wonderful. I mentioned tonight the Known issues and resolutions page Microsoft is maintaining for Flow – here is the link: https://ms.flow.microsoft.com/en-us/documentation/release-notes/#known-issues-and-resolutions There were a few questions about Flow during the meeting that I wanted to make sure I followed-up with – the list of questions & my answers are below: Can Microsoft Flow monitor list item changes while the Flow is running – meaning can another Flow instance start if a user updates a list item while the Flow is already running. It is my understanding that if the Flow is currently running on a list item, another instance of the Flow will not start when a trigger occurs. Is there a trigger in Microsoft Flow for item deletes? No, just like SharePoint Designer workflows, there currently isn't a way to detect item deletes. Is there a particular patch level for SharePoint 2013 that is required for Microsoft Flow to connect? I haven't seen documentation noting a specific service pack or patch-level that is needed, but I will ask Microsoft for clarification and post the answer here.

The post Cincinnati SharePoint User Group – June 22nd appeared first on Daniel Glenn.

Creating & Upgrading SharePoint Workflows – April 9th 2017

Daniel — Tue, 02 May 2017 22:36:42 +0000

I am excited to be speaking once again at the Nashville SharePoint Users Group. The meeting on May 9th 2017 is in-person and via online meeting and the topic is “Creating & Upgrading SharePoint Workflows”. The details of my presentation are below. For a long time, we have used workflow for automating business processes in every version of SharePoint, while using various tools to create them: out of the box workflows, SharePoint Designer, Visual Studio, & third-party applications like Nintex and K2. Now that SharePoint Designer will no longer updated and there is a push to move to the cloud, what are we supposed to do now to automate tasks and business workflow? What if you aren't moving to Office 365 and just want to know what tool you should use to create workflows moving forward? Should you migrate your existing SharePoint Designer workflows to Microsoft Flow or a third-party tool? What would that process look like? Should you continue to build workflows using SharePoint Designer in SharePoint 2010, 2013, 2016?In our time together, we will review those questions and more so you can be confident in your path forward with process automation, no matter what version of SharePoint you are using or where it is hosted! [UPDATE] I had a great time with the group tonight. There were some great conversation concerning the gaps between SharePoint Designer workflows and Microsoft Flow. Everyone stay tuned to this space and make sure you register for the May 16th Microsoft Virtual Summit. Learning about @SharePoint workflows from @DanielGlenn at @NashvilleSUG #GoCubsGo pic.twitter.com/IUhZ7A8aaL — Michael Hewitt (@mdhewitt83) May 9, 2017

The post Creating & Upgrading SharePoint Workflows – April 9th 2017 appeared first on Daniel Glenn.

Custom Filter on a Data View Web Part (series part 3)

Daniel — Thu, 30 Dec 2010 20:44:00 +0000

Data Views can be a very powerful tool when using SharePoint Designer 2007 in designing pages in your WSS 3.0 and MOSS 2007 environments (the same is true for SharePoint Designer 2010 and SharePoint 2010). One of the requirements for my project is to display documents from two different SharePoint Document Libraries in one view and have the documents displayed in a specific way. The content is to be displayed in the table view as follows: Document Icon Name Title Modified Date The Document Icon must display the file-specific icon, but the hyperlink must point to the file. [Go here to find out how I accomplished displaying the icon] The Name field should display the document’s name, but without the file extension [Go here to find out how I accomplished displaying the name without the extension] Only the last 30 days of modified files should be displayed. To filter the list of items in the Data View, first I setup the Data View to display the content like I wanted. Then, selecting the Common Data View Tasks drop-down (as shown below), I selected the Filter: option. The expression is pretty involved, but I cheated a little by using the Filter Criteria option. The expression I started off with was Modified Is Greater or Equal To [Current Date], as shown below. I then selected the Advanced button (shown on the picture above) and I was presented with the advanced expression being used by the builder. I added “- 30” without the quotes to the expression. The whole expression ended up being the one shown below: [number(translate(substring-before(@Modified,'T'),'-‘,”)) >= number(translate(substring-before($Today,'T'),'-‘,”)) -30]

The post Custom Filter on a Data View Web Part (series part 3) appeared first on Daniel Glenn.

Custom Column Data Display Names Using a Data View Web Part (series part 2)

Daniel — Thu, 30 Dec 2010 20:43:00 +0000

Data Views can be a very powerful tool when using SharePoint Designer 2007 in designing pages in your WSS 3.0 and MOSS 2007 environments (the same is true for SharePoint Designer 2010 and SharePoint 2010). One of the requirements for my project is to display documents from two different SharePoint Document Libraries in one view and have the documents displayed in a specific way. The content is to be displayed in the table view as follows: Document Icon Name Title Modified Date The Document Icon must display the file-specific icon, but the hyperlink must point to the file. [Go here to find out how I accomplished displaying the icon] The Name field should display the document’s name, but without the file extension Only the last 30 days of modified files should be displayed. [Go here to find out how I accomplished the filter] To show the name without the file extension, I added the Name field to the table, then converted the value to a Hyperlink. I then made the hyperlink value point to the file using @FileRef. To remove the extension from the display, I built the display value using two different expressions, as shown below: substring-before(string(@FileLeafRef), ‘.’) Working from the inside out, ‘string’ converts the filename variable into a string so the next expression can work with the value. ‘Substring-before’ accepts two variables: the data value and what character to look at for stopping (which is the period ‘.’). So, the full URL looks like: <a href=”{@FileRef}”><xsl:value-of select=”substring-before(string(@FileLeafRef), ‘.’)” /></a>

The post Custom Column Data Display Names Using a Data View Web Part (series part 2) appeared first on Daniel Glenn.

Custom Document Icon Using a Data View Web Part (series part 1)

Daniel — Thu, 30 Dec 2010 20:42:00 +0000

Data Views can be a very powerful tool when using SharePoint Designer 2007 in designing pages in your WSS 3.0 and MOSS 2007 environments (the same is true for SharePoint Designer 2010 and SharePoint 2010). One of the requirements for my project is to display documents from two different SharePoint Document Libraries in one view and have the documents displayed in a specific way. The content is to be displayed in the table view as follows: Document Icon Name Title Modified Date The Document Icon must display the file-specific icon, but the hyperlink must point to the file. The Name field should display the document’s name, but without the file extension [Go here to find out how I accomplished displaying the name without the extension] Only the last 30 days of modified files should be displayed. [Go here to find out how I accomplished the filter] To show the Document Icon, I added the DocIcon field to the table, then converted the value to a Hyperlink. I then made the hyperlink value point to the file using @FileRef. To point the DocIcon (which has a value of ‘PDF’, since all my documents were PDFs) link to the correct picture, I pointed to a pdf picture (pdf.gif) on my site. You could do this several ways, but I just put a PDF icon in a ‘system’ document library on my site. I also wanted to make my solution work if it was later decided to add documents to the displayed libraries that were a different type other than PDF. So, in the hyperlink, I used the @DocIcon field in the src value: src=”/site/system/{@DocIcon}.gif width =”17” height=”17” A couple things to note about the link above: 1) it assumes all the images will be gifs and will reside in the same document library and 2) the images are all shown with 17 pixel width and height. So, the full URL looks like: <a href=”{@FileRef}”><img border=”0” src=”/site/system/{@DocIcon}.gif width =”17” height=”17” /></a>

The post Custom Document Icon Using a Data View Web Part (series part 1) appeared first on Daniel Glenn.