Cross-Validation Rules Sourcing
Overview
Sourcing allows Cross-Validation Rules to apply to custom transaction fields within each company's unique NetSuite environment. Sourced fields can be used for Cross-Validation Rule Filters or Requirements.
Step-by-step process
Users can configure Cross-Validation Rule sourcing under Netgain > Setup > Cross-Validation Rule Sourcing. Cross-Validation Rules will come with pre-built sourcing for certain fields like Department, Class, and Location. Sourcing requires three values: Name, Transaction Field, and Source.
| Field | Description | Example |
| Name | The name that the user wants to give this sourcing record that will show up on Cross-Validation Rule dropdowns. It is generally helpful to use the same name as the transaction field. | Station |
| Transaction Field | This is the field on your transactions for the field you are setting up sourcing for. | Station (Line) |
| Source | This is the list or record that supplies the options to select for this transaction field on Cross-Validation Rules. It can be a custom list, a custom record, or a native record such as Department. See Available sources below. | Station |
In the example above, we have a custom transaction line field called Station that we use to categorize our transactions. The transaction field where users fill out a station on a Vendor Bill or Journal Entry is called "Station (Line)". The list of values that users can select when filling out "Station (Line)" is a custom list in our NetSuite environment called "Station." Based on this setup, when a user is setting up a Cross-Validation rule under Field for a Filter or Requirement, they will now see Station as an option. When Station is selected as the Field the options to select in the Value for the Filter or Requirement will be populated by the custom list Station.
Available sources
The Source dropdown lists the following, sorted alphabetically. Native record sources appear only when the matching NetSuite feature is enabled in the account.
| Source | When it appears |
| Account | Always |
| Subsidiary | OneWorld accounts |
| Department | Departments are enabled |
| Class | Classes are enabled |
| Location | Locations are enabled |
| Project | Projects are enabled |
| Custom lists | Every active custom list |
| Custom records | Every active custom record type, including the record behind each custom segment |
Choose a native record source (such as Department or Account) when your custom field points at that record instead of a custom list.
Supported field types
Cross-Validation Rules can only reference custom transaction fields that meet specific criteria. A custom field is eligible when it is a transaction body field or transaction line field and is stored (the Store Value box is checked on the field record).
The field's value type determines how it becomes available to a rule:
| Value type | How it is used in a rule |
| List/Record | Set up a Sourcing record as described above. The rule's Value then offers the options from the source list or record. |
| Free-Form Text, Integer Number, or Currency | Available directly in the Field dropdown for Filters and Requirements - no Sourcing record needed. |
Custom segments that are visible on transactions also appear in the Transaction Field dropdown when custom segments are enabled in the account.
Other value types do not appear in these dropdowns.
Checkbox fields are not supported.
A checkbox custom field has a value type of Checkbox, which is not one of the supported types (Free-Form Text, Integer Number, Currency, or List/Record). Checkbox fields will not appear in the Sourcing Transaction Field dropdown or in the Field dropdown for Cross-Validation Rule Filters and Requirements.
