Extended Requisites are custom fields users can create and add to tables on specific cards in FCX.

Because these are not programmed Requisites, they have limited functionality. For example: Extended Requisites cannot be added to a Reference View as Visible Columns.

ASIDE
Although Extended Requisites cannot be viewed as individual Columns in the Reference, they can be searched. This is possible using the “Digest” Column.
The Digest Column concatenates all Extended Requisite names and their entered Values on a card into a single long string for each Record. While the Digest Column is hard to read, it can be used to search by Extended Requisite Values.

Extended Requisites are very important to Asset Categories and their Assets for 2 reasons:

• You can use them to capture different data for different types of equipment.
• You can ‘code’ a Category Naming Convention to create an Asset name from its Extended Requisite Values.

An Extended Requisite set can be specific to each type of Asset.

For example:

• Pickup Truck Unique Extended Requisites:
  1. VIN
  2. Bed Length
  3. GVWR
• Laptop Unique Extended Requisites:
  1. Hard drive
  2. CPU
  3. Screen size

You can add any combination of Extended Requisites to an Asset Category card to make those fields available on Asset cards created under that Category.

IMPORTANT
In Asset Category Hierarchies, Extended Requisites are inherited!

Extended Requisites added to a Category will show on Asset cards created under that Category, but they will ALSO be shown on child Category Assets! This means, when you are looking at a child Category card, its Assets will get Extended Requisites you don’t see on this card, because they are coming from the parent Category!

 For more information on Extended Requisite Inheritance, see: Hierarchy & Inheritance.

Extended Requisite Categories are not connected to Asset Categories.

Extended Requisite Values

User types-in simple string by default.

Create Requisite Value Records to control input options.