Reviving a Lookup field in a published 'read-only' Content Type

A Lookup field as part of a Content Type in the Content Type Hub that is published will not appear in the other Site Collections because it's missing the link to the connected List.
But it's possible to revive this Lookup field in the published 'read-only' Content Type that's added to a List or Document library.

First add a list in the Content Type Hub and add an extra Column named 'Description' to it:

Create a Site Column of the type Lookup and connect it to the List:



Create a new Content Type based on Document:

Add the Lookup field to the Content Type:

Publish the Content Type:

The Content Type is now available in the other Site Collections.

But there is no Lookup field in the published 'read-only' Content Type.

Create a similar List and Lookup field with the same name in this or other Site Collection:

Add some items to the List:

Create a Site Column of the type Lookup with the same name (and typo) and connect it to the List:

Go to a Document library and set 'Allow management of content types' to Yes in the Advanced Settings, add the published Content Type to the Library and Set as default Content Type:

Add a new document to the Library; there is no Lookup field (yet):

Now 'Add from existing site columns' the local Lookup field:

It looks like the Site Column is not added to the read-only Content Type.



And here is the magic. The Lookup field is revived and is connected to the local List.

Drag and drop files between groups to update metadata in modern document libraries

There is a storm of changes and new features unleashed in Office 365 and it takes effort to keep track of it all ('Luctor et Emergo'). But something caught my eye when I read the What’s new in Microsoft SharePoint Online June 2016 Updates. A small note in the text, but one giant leap for users: Drag and drop files between groups to update details when you're in a view that groups files by metadata.

Adding metadata automatically is easy when document properties are promoted from the Office file to columns in SharePoint and/or default values are set for metadata at library and folder level. But once the document is there, it's always been a challenge to let users update the metadata for sake of document management and control.
Modern document libraries offer the possibility to edit the columns directly in the information panel and modern display form. Drag and drop could be the most userfriendly way to let you update the metadata so let's find out how (and if) this works.

I've created a number of "Group By" views in a document library:

Group by Choice field: it works!

Drag & drop the selected document(s) into the other group:

The update of the Choice field value is successful:

Group by Lookup field: error! this is fixed by the product team

The item wasn't updated; the following error occurs:

Group by Person field: it works!

Drag & drop of tiles does also work

Group by Managed metadata field: nothing happens! This is fixed by the product team as well !

I've submitted a service request in my tenant to find out more about the current shortcomings.
I'll keep you posted about the updates.

Update 28-11-2016: The error with (Group by) Lookup field is fixed by the product team; this works correct now. A new ticket for a hotfix is opened for the (Group by) Managed metadata field.

Update 20-01-2017: Drag & Drop to change the value of a managed metadata field is working now.