i need help understanding this thing. i was under the impression that fields that are created from custom types will always show up in the Document Information Panel in Office documents as disabled with the message "Edit property on server". am i mistaken? in either case i'm seeing some inconsistencies that i need help figuring out
i have 4 fields created from 2 custom types. in our development environment they're disabled in the DIP. in our test environment they're not. both environments are using the same custom field types and custom document libraries. why would these fields be disabled in one and not the other? i know you can define a document library and not explicitly declare a custom field in the schema, but instead only include it in a content type and it may not be disabled in the dip, but this time all the fields are defined in the schema. so what else can affect this behavior?
i have 4 fields created from 2 custom types. in our development environment they're disabled in the DIP. in our test environment they're not. both environments are using the same custom field types and custom document libraries. why would these fields be disabled in one and not the other? i know you can define a document library and not explicitly declare a custom field in the schema, but instead only include it in a content type and it may not be disabled in the dip, but this time all the fields are defined in the schema. so what else can affect this behavior?