Hot answers tagged document-info-panel
4
This problem is caused by differences in the SourceID property of the metadata fields. If you compare the value of SourceID on a field of a content type in one library with the same field of a content type in another library you will see that they differ, and they are used inside the Word document when referencing the metadata field.
The solution is to set ...
4
No, because the SPServices Cascading dropdowns functions on list forms. To my knowledge, you can't specify metadata before creating a document. You could require check in/out on the document library to force an item be checked in before being available and this would let you use the SPServices cascading dropdowns since that's effectively an editform.
I'm ...
3
I've just made a small test of difference ways to create a word document in the file system and then use it to programatically create documents in a document library with properties.
Create not using SharePoint
Create document/template from scrach in Word. Add Custom properties. Add Quick Part using Field|DocProperty|Property. Save to file system
Result:
...
3
You do not have access to the DIP in Office Web Apps. Since you're using the web UI already it's easy to go the the item in the library and change it's properties there. If you need more advanced DIP's (for instance built with InfoPath) then you need to modify the edit, new and view forms of the page to get the "same" experience as in the full fledged Office ...
2
Before opening the form from the web uninstall the one you published locally. To do this open InfoPath, locate the form in the backstage view and uninstall it. InfoPath keeps a cache of forms that are installed and matches the location of the form to the one it knows it was published to. This is for security reasons, e.g. copying the form onto another domain
...
1
An InfoPath content type and a document content type are two different things.
InfoPath forms can be published as a content type, but they will be InfoPath forms. An item created from an InfoPath form content type will be an XML document.
You cannot easily use InfoPath forms to edit the metadata of a document content type. It's different with lists, where ...
1
My experience is that by default uploaded files remain checked out until all required metadata fields have been provided. The user cannot check the document in unless they fill in the fields. As long as the document is checked out, only the user who uploaded it will be able to see it.
Scenario: Document Library with two content types, one is the default ...
1
There is an article that describes a similar problem (it's about excel templates) and some workarounds.
http://bizsupport1.austin.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=1840603&prodTypeId=18964&objectID=c03474919
I haven't tried all these workarounds but it may get you started. I am dealing ...
1
I believe this is a bug. I have not found solution but I have workaround. I have split my content type into 2 content types. One has managed metadata columns I do not want to be displayed in DIP and another has columns that should be displayed. I added these 2 content types to my library and assigned the one without managed metadata to my documents. After ...
1
I haven't tried this in a document library, but you might find Column Validation a valid replacement for the InfoPath rules.
Ian Morrish wrote a good visual walkthrough of the new feature.
Only top voted, non community-wiki answers of a minimum length are eligible
