Objects
This page lists objects used by FieldFX and grouped by FieldFX module. Not all the objects are for FX5 and some objects need additional licenses to use. Some objects are background objects that function as data containers and have no user interaction.
It is intended as a complete object reference for administrators, architects, and integrators.
You can configure the following for each object:
| Configurable Item | Info |
|---|---|
Custom Fields & Relationships |
Fields in which you can enter data in records |
Lookup Filters |
Filters that control the records displayed in lookups |
Validation Rules |
Rules that prevent you from entering invalid data in records |
Page Layouts |
Layouts that control the fields on Detail and Edit pages |
Compact Layouts |
Layouts that control the key information displayed for records |
Search Layouts |
Layouts that control the fields in lookups and search features |
Buttons, Links, and Actions |
Options you can select to do something to a record |
Record Types |
Different types of records you can add |
Object Settings
Best Practice
Don’t use same or similar names for FieldFX standard objects, fields, and API Names. Using the same or similar names could cause performance issues in Salesforce platform and FieldFX.
Here are the master-detail relationships for key objects:
|
A
| Object | Object API Name | Info |
|---|---|---|
|
||
|
Asset Groups are used to categorize individual Equipment, Bills of Materials, Standard Work Order Tasks and Model Work Orders. |
|
|
The Asset Stock Issue History object is a Junction object in Master-Detail relationship with both the Equipment and Stock Item objects. This object is populated via APEX and contains a record for each Stock Item issued to a unique Equipment. |
|
|
||
|
Attributes in the Noun-Modifier MRO Inventory Attribute Tracking |
|
|
Storage for sync (upload) errors and other similar data. |
B
| Object | Object API Name | Info |
|---|---|---|
|
A Bill of Material is a list of Catalog Item records accessible from a work order that serves as a list of repair parts. |
|
|
Defines the Catalog Item records for a unique Bill of Material. |
C
| Object | Object API Name | Info | ||
|---|---|---|---|---|
Catalog Item (Part of the Base Package) |
|
A master catalog item. |
||
Chart of Accounts |
|
|||
|
||||
|
Master Object(s): Contact and Qualification |
|||
Credit Memo |
|
|
||
|
||||
|
|
|||
|
The Crew object is used to organize Crew Members (Users) into a single group. The Crews are selected on the (Scheduling) Dispatch Console and the Crew Members will be populated as Resources on the Timeline. |
|||
|
||||
|
||||
|
||||
|
The Credit Memo functionality in FieldFX has been deprecated. Contact your account representative for another solution. |
D
| Object | Object API Name | Info |
|---|---|---|
|
||
|
This object can be used for deep copying any custom sobjects, managed or unmanaged and to queue up the deep copy requests. The requests would be run sequentially by a single process and avoids locking on sobject entities, for example lock on CatalogItem at PriceBook cloning. See FXL Deep Copy for more information. |
E
| Object | Object API Name | Info |
|---|---|---|
|
||
|
||
|
This object tracks the actual equipment that is scheduled on the job. It will eventually be used to track non-job locations for equipment as well such as repair shops or inspection facilities. |
|
|
||
|
This Error Log object is used to log all the exceptions that are thrown from apex code inside the EAM managed package and to record errors encountered in managed flows. |
|
F
| Object | Object API Name | Info |
|---|---|---|
|
||
|
||
|
Metadata for the Advanced Forms in DataGuide. See ServiceMax DG Form for more information. |
|
|
Defines fields of an object to which keywords to be applied. See ServiceMax DG Form Criteria for more information. |
|
|
Contains the raw json result of a form, either completed or still in progress. See ServiceMax DG Form Data for more information. |
|
|
See ServiceMax DG Form Expression for more information. |
|
|
Used to indicate that a form, where the Multiple Technicians checkbox is set to true, is claimed for edit by a user for a specific target record. See ServiceMax DG Form Lock for more information. |
|
|
See ServiceMax DG Form Report Template for more information. |
|
|
See ServiceMax DG Form Response for more information. |
|
|
This is a child of the Form object and contains the actual form definition to be used with the metadata in the Form object. See ServiceMax DG Form Version for more information. |
|
|
This object acts as a junction object between the Form Version Object and Tag Object. See ServiceMax DG Form Version Tag for more information. |
|
|
Stores a collection of configuration items. |
|
|
||
G
| Object | Object API Name | Info |
|---|---|---|
|
The GL Detail is use to capture a single entry General Ledger Transaction which can subsequently be transferred to an accounting solution and posted as a journal entry. |
|
|
The GL Variables serve to support sub ledger account segment used as a company, cost center, asset, work order, etc. |
I
| Object | Object API Name | Info | ||
|---|---|---|---|---|
|
The Inventory Location Contains the On Hand Qty for an Inventory Item Record. |
|||
|
Stock Inventory Transactions. A user may enter a Gain/Shrink/Issue type transaction. Order and Receipt type transactions are entered programmatically thru APEX and should NOT be manually entered. |
|||
|
|
|||
|
Master object(s): Invoice |
|||
|
Contains the Catalog Item Attributes for the Catalog Item based on the selected Noun-Modifier. |
|||
J
| Object | Object API Name | Info | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||
|
Tracks safety compliance for each job. |
||||||||||||
|
|||||||||||||
|
This custom object is for Job Log Records. |
||||||||||||
Validation Rules (See Validation Rules) |
|
||||||||||||
|
This object lists the records for job resources. |
||||||||||||
CASE( Text(FX5__Catalog_Item__r.FX5__ffx_Item_Type__c) , "bulk consumables", FX5__Qty_Delivered__c - FX5__Qty_Consumed__c - FX5__Qty_To_Be_Returned - FX5__Qty_Returned__c , "bulk asset", FX5__Qty_Delivered__c - FX5__Qty_To_Be_Returned - FX5__Qty_Returned__c , "serialized asset", FX5__Qty_Delivered__c - FX5__Qty_To_Be_Returned - FX5__Qty_Returned__c, "serialized consumable", FX5__Qty_Delivered__c - FX5__Qty_Consumed__c - FX5__Qty_To_Be_Returned - FX5__Qty_Returned__c, "service", FX5__Quantity__c - FX5__Qty_Consumed__c, "labor", FX5__Quantity__c , 0 ) |
|||||||||||||
Description: Daily snapshots of Job Resource status and quantities for historical tracking and trend analysis. |
|||||||||||||
|
|
||||||||||||
M
| Object | Object API Name | Info | ||||
|---|---|---|---|---|---|---|
|
A Meter is used to track time (hourmeter), distance (odometer), cycles (cumulative cycle counter) or usage. Meters can be used to schedule preventive maintenance. |
|||||
|
Meter Readings are used to record time (hours), distance (odometer readings) or usage (cycle counts) for a Meter on a specific Date/Time. |
|||||
|
|
|||||
|
The Mobile Sync Log object is used to track the logs of mobile syncs every time a mobile device syncs with Back Office. |
|||||
|
Modifier Object in Noun-Modifier MRO Inventory Attribute Tracking |
|||||
P
Payment | Payment Applied | Planned Stock | PM Group Detail | PM Route | PM Schedule | PO Misc Cost | PO Misc Cost Receipt | PO Stock Item | PM Criterion (Deprecated) | Price Book | Price Book Assignment | Price Book Item | Price Book Item Service Type | Purchase Order | Price Book Item Service Type
| Object | Object API Name | Info |
|---|---|---|
|
||
|
||
|
The Planned Stock record is used to record the Planned Qty of a Stock Item for a Work Order. This record (Open Commit Qty) is used as demand input for parts commitments (reservations). Also used to record Planned Inventory Cost vs. Actual Inventory Cost. |
|
|
PM Group Detail specifies the PM schedule to run for any given Monthly Interval e.g, every month, quarter or annual etc. This object stores information as to when the PM Schedule on an Asset is due next, current Work Order etc. |
|
|
PM Routes are used to organize PM Route Stops which are comprised of an Equipment and a Standard Work Task. The PM Route contains calendar based scheduling logic to create and release Route & Route Stop Work Orders in a Parent/Child relationship. |
|
|
Preventive Maintenance Schedules are used to schedule & release Work Orders using a Model Work Order as a template and a predefined Calendar or Meter Interval. |
|
|
Purchase Order Miscellaneous Cost Line - Represents all lines that are not linked to Stock Item inventory |
|
|
PO Misc Cost Receipts are recorded to recognize the receipt of a Service / Non-stock Part. A PO Misc Cost Receipt will automatically record a Work Order (WO) Misc Cost Receipt if the PO Misc Cost record is linked to a WO Misc Cost record. |
|
|
Purchase Order Lines for Stock Item Inventory |
|
|
Custom |
|
|
Don’t grant FieldFX users write access to this object in permission sets, just read access. |
|
|
||
|
||
|
Master Object(s): Service Type |
|
|
Purchase Order Header |
|
Q
| Object | Object API Name | Info | ||||
|---|---|---|---|---|---|---|
|
||||||
|
Master Object(s): Qualification |
|||||
|
New Fields: |
|||||
|
|
R
| Object | Object API Name | Info |
|---|---|---|
|
This object describes a template for various reports, primarily for Mobile users. |
|
|
||
|
This object contains the criteria used to apply actions in the CPQ module. Master Object(s): Price Book |
|
|
These actions are triggered by the criteria on the Rule object for the CPQ module. Master Object(s): Rule |
S
Object |
Object API Name |
Info |
|
Master Object(s): Equipment |
|
|
||
|
For more information, see Staged Data. |
|
|
Standard Work Tasks serve as a Library of predefined Work Tasks which may be selected and applied to a Work Order. The Work Task Description, Planned Hours and Instructions are copied. |
|
|
The Standard Work Task Steps are used as checklist items on a Work Task. |
|
|
This object stores the master list of statuses for all entities using record types. Note that not all status attributes are applicable to all entity types |
|
|
||
|
||
|
The Stock Item object contains a lookup to the Catalog Item (catalog master) and the Warehouse (warehouse) and is where all of the inventory stocking policies for a specific Item in a specific Warehouse are managed; i.e. min stock qty, on hand qty, bin locations, preferred vendor, costs, etc. |
|
|
User’s Syncable Jobs. |
|
|
This controls which data the mobile client users will receive when they sync. Users will only get information related to the offices listed here. |
|
|
||
T
| Object | Object API Name | Info | ||||
|---|---|---|---|---|---|---|
|
Master Object(s): Job |
|||||
|
||||||
|
|
|||||
|
||||||
|
||||||
|
||||||
|
The Transfer Order is used to support inter-Warehouse sourcing for Stock Items. |
|||||
|
The Transfer Order Line represents a single Stock Item on a Transfer Order. |
|||||
|
The Transfer Order Transaction object represents the fulfillment or receipt of Stock Items on a Transfer Order Line. |
U
| Object | Object API Name | Info |
|---|---|---|
|
The UNSPSC is a four-level hierarchical classification system; Segment - Family - Class - Commodity used to categorize goods and services. For more information, see UNSPSC Taxonomy. |
|
UNSPSC Commodity |
|
|
UNSPSC Family |
|
|
UNSPSC Segment |
|
|
|
||
|
||
W
|
The Warehouse Item record has been deprecated and is no longer supported or updated. Use the Stock Item record instead which requires a FX EAM license. Once FX EAM is installed, follow the steps in to add stock items. |
| Object | Object API Name | Info |
|---|---|---|
|
||
|
||
|
Work Order (WO) Miscellaneous Costs are used to record charges against a work order that are NOT labor derived from time entry (i.e. Task Labor records) or issued parts (Actual Costs on WO Parts). |
|
|
Work Order Misc Cost Receipts are recorded to recognize the receipt of an expense item/charge to a Work Order. This receipt record can be automatically recorded from a Purchase Order if the PO Misc Cost Line is linked to the WO Misc Cost. |
|
|
The Work Assignment object is used to represent which users are assigned which Work Tasks, and optionally when they are to scheduled to perform the work. |
|
|
The Work Order is the top level work document and is where costs are accumulated. A Model Work Order serves as a job template used in Preventive Maintenance Scheduling. |