Allow custom field database query to specify what field(s) populate pull-down list

[GeorgeJ4336]

Custom (user-defined) fields for matters are very handy. A particularly handy feature is the ability to use a matter or contacts database query to define a list of selectable values for a drop-down list. Such a query returns the contact(s) or matter(s) that match the query. For example, (Role = "Inventor") returns a list of contacts who are inventors. (The parentheses are not necessary. I used them here merely for clarity. Custom fields are described in this AppCol help article.)

Custom fields would be even more powerful if the query could specify some other field(s) in the matching record(s) to populate the drop-down list.

For example, I have several USPTO customer numbers, because some of my clients want me to use specific customer numbers for their work, so they can access their applications via Private PAIR or Patent Center. I can create a custom field called USPTOCustomerNumber and manually populate it with a list of my customer numbers.

However, this field would be much more powerful if it could be defined via a contacts database query, such as (USPTOCustNum <> ""), that returns not the contact, but {Contact.USPTOCustNum}. That way, the pull-down list would automatically include all client-specific customer numbers.

I suggest a syntax along the lines of:

(USPTOCustNum <> "") (Returns {Contact.USPTOCustNum})

Bonus points if the "Returns" clause accepts syntax to concatenate several fields and format returned values.

When pulled down, a custom pull-down field defined with a database query currently displays some handy context information (name or client code, role), which helps in choosing an appropriate entry from the list.

Additional bonus points for syntax to control what gets displayed in the pull-down list, for example:

(USPTOCustNum <> "") (Displays {Contact.Company} {Contact.USPTOCustNum}) (Returns {Contact.USPTOCustNum})

In contrast, a plain pull-down list of customer numbers (without a database query) does not provide any context information.

Further bonus points to add a "Displays" feature to the List-type of drop-down custom field definition syntax.

Thanks,
George

[support_appcoll]

Thanks for the ideas - very interesting. We'll pass it onto engineering for consideration.

AppColl Support