cancel
Showing results for 
Search instead for 
Did you mean: 

using 'residual' properties

abruzzi
Champ on-the-rise
Champ on-the-rise
Recently, I discovered that I can create a property of cmSmiley Tongueerson that isn't defined in the cmSmiley Tongueerson document model.  It shows up as a "residual" property in the lucene search, and it is still query-able.  I'm curious what the properties of these residual items are?  I'd rather not hack on the core definitions in alfresco–it makes a maintenance nightmare when you do upgrades, and (for the moment) I just need to attach a employee ID to the cmSmiley Tongueerson during the LDAP sync. 

So if I use a property name the alfresco coders will never use like "DAC_employeeID" is this reasonable, or is it a bug that may be quashed at any moment?

thanks,

Geof

EDIT:  I should add that I don't need users to see these, and don't want them to edit these.  I just need scripts to be able to retrieve these and lucene searches on these fields to work.
1 REPLY 1

mrogers
Star Contributor
Star Contributor
As you have already found, a "residual" property is a property which is not defined in the data dictionary.     I don't think its a "bug" that is going to be fixed.

Perhaps another approach to consider would be to to add your own namespace, dac, and define an aspect that contains dac:employeeId.   Then you would not need to worry about variable name clashes.