Tag Info

Hot answers tagged

2

Based on my testing and experience that is expected behavior of versioning and look up columns. As you can see in the Versioning Settings of the library, the Document Version History option is described as following: Create a version each time you edit a file in this document library? Now changing the value of the list item only affects the list ...


1

You need to map the crawled property for the column to one of the existing RefinableString... managed properties. This is due to a limitation in SharePoint Online where you can not mark additional managed properties as refinable (as you can do on prem) Detailed instructions here: ...


1

You can use count related lookup column. Below is the link for reference: How to create count related lookup column


1

Alternatively, you can provision your lookup column with a feature receiver everytime you create a new website. You just need to make sure you have the lookup list available somewhere (which, by the way, CAN BE in a different web site). There is a quick and easy to implement guide which you can find here: ...


1

Lookup columns will only lookup data in lists in the same site/web. When the content type hub functionality deploys your content type to other sites, the lookup list does not exist there, so the column is removed. The best way to do this is to use a managed metadata term set instead. The term set is globally available to all site collections. So you can add ...



Only top voted, non community-wiki answers of a minimum length are eligible