Forum Discussion
Ondřej Mařík
May 22, 2017Copper Contributor
Sharepoint Online - Acces search field of document set from word document
Hello,
We are trying to setup following scenario.
I have created custom content type (document set) with name PROPOSAL which contains column CUSTOMER - search field from another shapeoint list.
In properities of this column is checked that in every view where column is used it should automatically add also name and VAT number properities column.
The CUSTOMER column is also marked as shared in a document set properities.
Now I would like to create word template for PROPOSAL where I will use CUSTOMER:Name property in text. The problem is, that in a quick fields insert is only field customer and when I use this one, it puts ID of the record in the text not its name.
Is there a way, how to acces sub fields in a document?
Thanks a lot for help.
- Brent EllisSilver ContributorI'd consider making a workflow that copies the values of the fields you need into "Single Line of Text" fields in the document set. I don't think you can get it any other way. Word is tricky in what it allows you to use and not use.
- Ondřej MaříkCopper Contributor
Yes, I was thinking about it but do I have any options how to make these fields hidden and shared? I tried to use sharepoint designer for editing new and edit form but I can't edit it in custom content type.
- Brent EllisSilver Contributor(This may not exactly match what you are trying to do), but I would create the fields (we'll call them Field X and Field Y) at the Document Set level. Have a SharePoint Designer workflow to set the Field X and Field Y values (based on the lookup) everytime the Document Set details are modified. Then in the Document Set Settings, set Field X and Field Y to be inherited by all sub-content types. Then in the content type INSIDE of the Document Set, set field X and field Y to be "hidden", so users couldnt attempt to overwrite them. They don't have to be hidden at the Document Set level cause your workflow is re-setting them every time regardless.
- Agree with Brent's workaround, very valid!!!