Custom collections

Before making any changes to custom collections:
1. All users other than the administrator should exit the PDXpert application.
2. The administrator should close all open data records (Item | Close All).

Purpose §

Defines a constrained list of choices to be displayed within a custom attribute.

Where used §

Custom attributes in documents, parts, change forms

Data fields §

Collection §

Name §

This is the custom collection's name within the Custom group.

It's permitted — but not recommended — to assign the name of a standard collection, such as Persons, to a new custom collection. Future PDXpert capabilities may rely on unique collection names, and duplicate names may need to be renamed later.

Description §
This describes the function or purpose of the collection.

Collection member §

Name §
This is the complete name for the collection member.
Abbreviation §
Specifies a short version of the member name. Although not used within the application, that database value may be available for export via a Data Transformations object.
Description §
This describes the function or purpose of the member.
Custom collection §
Identifies the collection that contains the member. When first creating the member, you can move it to another collection; however, after saving, the member can't be moved.
Active: users can select
Default member of collection §
For a description of these checkboxes, see the Collections reference > Managing collections help topic.
The first member of the collection will be assigned as the default. If the collection has more than one member, the default can be changed to a different member.
Making a custom collection member inactive makes it unavailable for new assignment, but doesn't remove it from any items where it's already used.

Setup suggestions §

A custom collection defines a fixed set of choices that can be selected in your items' custom attributes.

Always create a generic record, such as Not specified, as the default collection member. When creating a custom attribute in a part type, document type or change form template, assign this generic member as the default. The value is displayed until a useful collection member is intentionally assigned to the item.

Custom collections can be created to meet a very specific need, or to be broadly reusable. For example, if you want to create a list of possible paint colors for a part, the custom collection might be called either Colors or, more narrowly, Paint colors. The choice affects the number of collections, and how you'll manage each one over time. Consider whether:

  • the collection can be used for different purposes — that is, the collection members are generic (Red) or specific (Copper Sunset) —, and
  • modifications to the custom collection's members — say, new colors — will be appropriate wherever the collection is used.

2001

Learn More
Help Guide Contents [PDF]