We have a customer who is using Colligo Engage for Outlook, uploading emails to SharePoint Online and tagging them with some additional metadata for other departments to keep track of what is occurring.
All of that is well and good but the name column was just too long to display along with all the other columns in the library view. This is a pretty common problem with long file names and one you can usually solve with users who are uploading traditional files but with this process they didn’t modify the file name Colligo automatically generated.
This post covers creating custom reports from SharePoint lists in Excel by joining SharePoint lists together. It specifically addresses the issues with People Picker and Lookup columns returning the row ID rather than the value. Continue reading
As an active Microsoft partner (The Full Circle) we’ve participated in a number of Early Adopter and Technical Adoption Programs over the years for several Microsoft server products going back to Windows Server 2008.
We continue our commitment to keeping up to date with the latest Microsoft technologies including client O/S’s, the latest being Windows 10 scheduled for RTM in a few weeks time, July 29th
We also use our computers like our customers do – AD domain joined, centrally managed and monitored, etc.
Windows 10 has continued to improve synchronisation across multiple devices and platforms – today’s world includes several clients – Smartphones, Tablets, Desktops, etc.
Keeping user/profile elements such as Themes, passwords, IE favourites & history, etc. in sync is expected by all.
However, in Windows 10 this functionality like in Windows 8, relies on using a Microsoft Account to work.
SharePoint’s user interface can be misleading at times. So when asked how you view previous version of a document without having to make it the most recent version , you’d think you’d just click on “view” and boom, you’d see the earlier version… No. All you get is the Document Properties history.
Here is how it is done.
A customer recently reported that passwords changed on premise weren’t being reflected in Office 365. Running a full sync in the FIMs client was the solution.
Emergency support can be a bit stressful, especially out of hours on a system you’ve never worked on before.
We recently needed to step in to help a customer who’s 2 node SQL cluster had gone down late one night and managed to get it backup in a few hours after a major disk corruption on the data and logs volume of cluster shared disks taking our the system databases and the user databases. Continue reading
As part of some investigations into SQL Server Database Mirroring I did this diagram to show how it works and the pro’s and con’s.
While mirroring is deprecated and will be removed in future versions of SQL server, it is still there in SQL 2014 virtually unchanged and is a good solution for customers with Standard Edition and who can’t or won’t use clustering (SQL clusters aren’t supported in Hyper-V replicas).
We noted that DirSync wasn’t working for one of our customers, new users weren’t being provisioned in the cloud and there were errors in the event log about FIMS and DirSync.
We’ve now invited about 30 external people into our SharePoint Online customer sites and have seen this enigmatic error pop up twice. Continue reading
This is a situation we resolved for a customer who was having issues when external people were trying to send to some of their distribution groups.