mercredi 20 juin 2012 20:43
I have a custom content dype based on the document content type. The custom content type has a word template uploaded to it and may columns base on existing site columns. The question that I have is show I be able to go to the custom content type and edit the template and see those columns as document properties?
I do not see the document properties in the contnet type I do see the document properties when I add that content type to a document library. The problem is that I am adding those properties as fields to the word document. I can only do that in the document library content type advanced properties and not in the site contnet types. by doing it in the doc library if I changed the tempate in the content type it overrides my changed in the library.
I am just not sure why I can not see those document properties when looking at the tempalte in site content types.
Than kyou for any help
Toutes les réponses
jeudi 21 juin 2012 09:49Modérateur
i can reproduce what you describe:
1.create a site content type docc1 inheriting the out of box document content type;
2.add a site column spouse to content type docc1;
3.upload a Word docx file as template for docc1; Edit the template; I can see that the template is stored in folder http://mysharepointsite/_cts/docc1/theTemplateName.docx; and i cannot find the spouse property in the Word document;
4.add the docc1 site content type into a document library, a list content type named docc1 will be automatically generated, inheriting the site content type, and the Word template is copied to the http://mysharepointsite/documentlibraryname/Forms/docc1/theTemplateName.docx; if i edit the template, i can find the spouse property in the Word document.
But my question is why do you need the custom property (spouse in my case) in the site content type? The property promotion and demotion works well without it.
- Marqué comme réponse GuYumingMicrosoft Contingent Staff, Moderator lundi 25 juin 2012 01:40
jeudi 21 juin 2012 13:30
I am not sure what you mean by property promotion and demotion.<o:p></o:p>
Here is my example;<o:p></o:p>
I have 4 word templates that are forms for loans, so I have fields like barrower, Investor, Loan Officer etc. These 4 templates would all use the same feeds/doc properties. The templates are all content types based off the document content type like I stated above, where the site columns are added to the custom content types.<o:p></o:p>
Does anyone know if the outcome that I am getting is the intended outcome from Microsoft?
I am asuming that I should just modify the template from the document library and not the content type... but that sounds strange to me and could cause problems if someone did change the tempate from the content type
vendredi 22 juin 2012 01:43Modérateur
property promotion and demotion means the columns in SharePoint document library will be synchronized with the properties in documents: http://msdn.microsoft.com/en-us/library/aa543341.aspx ;
I am asuming that I should just modify the template from the document library and not the content type
I think you mean modify the template from document library content type and not the site content type. But how do you modify? the columns in content type will appear as property in document template automatically.
vendredi 22 juin 2012 13:01
Yes, modify the doc library content type and not the site content type. The one detail that i did not mention is that I am adding the document properites as fields (quick parts) so as they are filling out the form they are filling the doc properties. My original plan was to manage those templates and fields in the site content type but I think I just needs to be managed/changed in the document library content type.
Thank you for talking this out with me.
samedi 23 juin 2012 02:52
You first have to create content types on the site level. Then go to a library where you want this content types and in "advanced settings" allow the management of content types. Then add only those content types from the site level that you want in this library. In other words, you might have 100 content types on the site level, but you can choose only few of them for a specific library. If you want to make changes to properties across entire site, you make these changes in the content types on the site level and these changes will be carried across the entire site. If you want to make changes to properties in one library only, then make changes only in this library. These changes will not be carried across the entire site.
Properties in "word" document will not be carried over to SharePoint. You will have to enter them manually.
samedi 23 juin 2012 05:08
See if my post http://parwejpathan.blogspot.in/2012/04/sharepoint-create-list-template-list.html helps!!
Thanks, Parwej http://parwejpathan.blogspot.com