[APBeta] User-defined Field explanation

Paul Rodman paul at ilanga.com
Wed Feb 18 20:36:02 PST 2009


Folks,

There is some confusion about user-defined fields in V2. They are a  
bit more complex than in V1, but are also much more general and  
scalable.

Executive summary:

You can (only via a script, currently) add an arbitrary USER FIELD  
(i.e. a named parameter with an attached value) to an item (Object,  
Observation, Resource, etc). It will appear in that item's list of  
user-defined parameters. However, in general, it will not appear in  
any other item's parameter list, nor (in the case of Objects) will it  
be available as a user-defined column. An item can have as many user  
fields as you like.

You can also add a USER FIELD DEFINITION either via a script, or by  
right-clicking a user-defined fields list. This definition will be  
global to all similar items (Objects, Observations, etc). The user- 
defined field list for the items will show the named parameter, even  
if no value has been assigned for a particular item. In the case of  
Objects, you can also define and show a column in the Object list for  
any user field definition.

User fields with an associated user field definition appear in black,  
"orphan" user fields without a definition appear in blue.

Typically, to add manually a new user field, you need to create a new  
user field definition by right-clicking the user-defined fields list.  
Once that's done you can edit the associated values.

Note that user field definitions for Objects are local to each plan  
document. All other user field definitions (Observations, Observation  
attachments, Resources, etc.) are global to the application.

You're probably more confused than ever now. Don't worry, you'll get  
used to it.

Paul R.




More information about the APBeta mailing list