The Baretta

What:  Surprisingly had some trouble with this simple task, so here's how you can avoid wasting 20 minutes of your life.  If you have a list column that is of type Date AND Time, it can be difficult to set it to the current date and time inside a workflow. Why:  You might like to do this if you were logging changes to items to a separate list for reporting on later. How (quick): Create a string variable called 'CurrentDateTime', set the string variable to equal 'CurrentDate[space]CurrentTime'.  Set your DateTime list column to equal the workflow variable CurrentDateTime. How (detailed): Create a Workflow Variable called ' CurrentDateTime ' of type ' Single line of text ' Create a 'Set Variable' step and set CurrentDateTime to equal value: Current Date[space]Current Time (these two values can be found under common variables tab). Update the field on the list item to equal the Workflow variable you just set.  In my ...

Sorry, something went wrong Field type [FieldName]  is not installed properly. Go to the list settings page to delete this field.   This is caused when a FieldType has been created usually via a custom solution (WSP), and has been used somewhere, then uninstalled while still being used somewhere on the Site Collection.  This error message is similar on all versions of SharePoint 2007/2010/2013. Usually you will have one or more Site Columns that are using the FieldType, and possibly one or more Content Types that are using that Site Column, and then most likely one or more Lists/Librarires using the Site Columns or Site Content Types. If you want to remove the Field Type Completely, steps to resolve are as follows: Try to delete the Site Column or Content Type from every list it is being used on.  If you can't delete the Content Type from the list, you will have to delete the list. Delete the Content Types using the Site Column (Site Actions >...

Earlier today I wanted to modify the address of the 'Pages' library on a SharePoint 2010 site.  The reason behind this was to make the naming of the folders more user friendly for our developers who would be deploying reports there. There wasn't a way to do it from the standard GUI, so I decided to modify it in SharePoint Designer (Hey, if SP Designer allows you to do it via GUI, it's safe right? ... right!?). Bad move, as there's some behind the scenes magic that must be hard-coded to the Pages URL, which breaks the Navigation Settings page (this one: http://[sitecollection]/_layouts/AreaNavigationSettings.aspx). 'An Unknown Error has Occurred' - Great.. I'm sure there would be a way around it, but for the sake of saving a few hours of investigation, don't change the name of your Pages Library! Ciao ciao!