In this article, I share three options for building cascading, menu-driven drop-downs in SharePoint Online/Office 365.
Option 3: Customize in PowerApps
OK, for the real cascading menu, you will need to use Power Apps. It is not something that you can do quickly or easily, like with the options above. You will need to get familiar with Power Apps and some minor coding. Since this falls outside of the “out of the box” solution, I would like to share the technique documented by others who are true experts in this area.
When creating a new page a header with the title of the page will be shown to the user. In the current days, it’s not possible to remove that header from the page using the SharePoint interface. Today, we will share a PowerShell that allows you to remove that area from the page and some article that you can use with different options.
Replace the variable below with your own and you will have a page without the title header.
In addition to your “Deactivated” field, create a Calculated field named “ActiveTitle” (or whatever you want to call it). Use the following formula:
The ActiveTitle field will be empty when the Deactivated field is set. When you configure your lookup column, tell it to use the value from ActiveTitle instead of Title. Empty values will not show up in your lookup list, so you will end up with only the values that are not Deactivated. Let me know if you have any trouble.
FIX: SharePoint 2013 Workflow recursion prevention – Part 2
7 minutes to read
Following FIX: SharePoint 2013 Workflow recursion prevention – Part 1, this post will walk you through the processes of designing your workflow that creates a list item on another list and invokes the workflow associated with that list using the new REST APIs released through SharePoint 2013 May 2014 CU as pointed out in part 1 of this series. If you haven’t read through part 1 of this series I suggest you do to get some background that will help you appreciate this post.
List1 has a workflow Workflow1 associated with it.
Workflow1 can be set to auto-start on item adding/updating or set to manually start or both, it doesn’t matter.
If the screen width less than 900 pixels we see dots instead of the value:
On a large screen we see the value:
Sample #2. Show values in one line
SharePoint list or document library view can contain columns with a large text inside. This leads to the fact that the rows in the view can be of different heights, which makes it inconvenient to work with data. With the new JSON formatting capability, it’s possible to show any column in a single-line with no wrapping.
The following formatting makes the cell value to be in a single line:
SharePoint Modern UI has a small gap: lookup column is empty if the field to show (Title column by default) is empty. JSON formatting allows provides us a workaround to show the ID of the lookup item in case the value is empty.
The following sample is to apply the workaround (show @currentField.lookupId if @currentField.lookupValue is empty):
The ability to save site as a template may be missing in SharePoint at times. This article explains why it might be missing and what your options are.
The most common reason that people notice the “Save site as template” option missing in SharePoint has to do with the enabling of SharePoint publishing feature. When you enable the SharePoint Server Publishing feature, it disables the ability to save the site as a template.
The Consequences of Deactivating Publishing
While it’s possible to save a publishing site as a template if you temporarily deactivate the publishing feature, it will be a huge mistake. I don’t recommend you use this workaround under any circumstances. This could be a recipe for disaster because although saving the site as a template would work fine, in the future when you try to use a template that was created by deactivating the publishing feature, you are likely to have all kinds of problems. Among other issues, you may see the following error message:
Provisioning did not succeed. Details: Failed to initialize some site properties for Web at Url: ‘……’ OriginalException: Failed to compare two elements in the array.
For all practical reasons, a template that was created by turning the publishing feature off, should be considered “infected with bugs” that are going to bug you (no pun intended) down the road. Technically they are not bugs at all, it’s just that the publishing feature contains certain site elements that a site template doesn’t support. In other words, once you enable publishing on a SharePoint site, there are components that can’t be turned off, even if you disable publishing. That’s why it’s so important that you plan your SharePoint deployment BEFORE you deploy SharePoint on your network.
WARNING! Avoid deactivating the publishing feature just so you can save the site as a template.
If you accidentally enabled publishing or community feature on a SharePoint site, you are better off saving your site content, deleting the site, and creating a new site with the appropriate template. Keep in mind, that when you delete a site, all content will be lost. You won’t be able to go to the Recycle Bin and recover your data.