Lookup columns include workflow status columns, traditional lookup columns to other lists, and person/group columns. This includes the two default people fields “Created by” and “Modified by”. If your list has more than 12 of these, you may receive the following error:
“This view cannot be displayed because the number of lookup and workflow status columns it contains exceeds the threshold (12) enforced by the administrator.”
In SharePoint Online, you’re not able to increase the lookup column limit. Lists created prior to the June 2013 CU update are capped at 8 lookup columns, while those afterward are allowed 12.
However, on-premise SharePoint (server) allows you to change this limit to your heart’s content.
You might run into this issue when running task processes in SharePoint Designer.
“Reason: The user who attempted to complete the task is not the user to whom the task is assigned.”
Assuming the person should actually be able to complete the task, check the following:
Make sure the user who was assigned the task does not have multiple accounts. If they do, the task could have been assigned to the account that the person isn’t currently signed in as when attempting to complete the task.
If it’s someone completing the task on behalf of another, make sure that individual is either:
A Site Owner (site settings, site permissions, people and groups, site owners) or
Task process owner (in SPD 2010 workflows, go to the properties for the task step and set task process owner. Click OK and republish workflow.):
Even if your SharePoint site’s regional settings are correct (or whichever data source you’re pulling from), Power BI could convert it to the wrong time zone upon import. It’s a quick fix, luckily. Instead of using your “modified,” “created” or other date field in your report, we’ll create a new calculated column in Power BI to use with an accurate time zone.
If you’ve seen a similar notification, I empathize with your pain. I don’t know that there is one solution to this problem, either, so I’m going to share a number of them we’ve used and hope that one (or all) of them will help you.
Basically a file is added through file explorer (a cloud library in OneDrive or SharePoint being synced locally to your computer) but then after a moment a notification appears which says “You now have two copies of a file; we couldn’t merge the changes in [filename]” and then the filename is appended with your computer name again and again until eventually the filename is too long and is harder to delete. Let’s not get to that point.
It’s not uncommon to want to use yes/no checkboxes when building Microsoft Flow conditions. [Field] is equal to “Yes” or [Field] is equal to true won’t work because it reads the Yes or true as a string rather than a value. So when the flow runs, even if the checkbox is checked (true), the run history says the expression result was false.
Fortunately it’s a simple two-step fix. Follow these steps to be able to use yes/no checkboxes as conditions in your flows: