This article explains how QBL handles these field types in legacy form rules:
- Lookup proxy
- Reference
- Lookup reference
- Reference proxy
Lookup and reference fields in form rules
When creating a form rule in Quickbase, you define a condition and an action. If you select a lookup proxy, reference, lookup reference, or reference proxy field, you have the option to select one of three values: the value in the field, blank, or browse choices.
This selected value is represented as QBL as follows:
1. The value in the field—References another fields
When:
- Type: QB::FormRule::Trigger::Field
Properties:
Comparison: IsNotEqualTo
Field: !Ref
Field: $Field_Flower_Common_Name
Value: !Ref
Field: $Field_Care_Rating
2. Blank—Default value
When:
- Type: QB::FormRule::Trigger::Field
Properties:
Comparison: IsNotEqualTo
Field: !Ref
Field: $Field_Flower_Common_Name
Value: Blank
3. Browse choices—References a record from the related table
When:
- Type: QB::FormRule::Trigger::Field
Properties:
Comparison: IsNotEqualTo
Field: !Ref
Field: $Field_Flower_Common_Name
Value: 4
Note: In the case where a different value other than Blank or a number is received, the QBL defaults it to Blank.
Unsafe record ID warning
When you use QBL to represent a legacy form containing one of these field types, the API raises an UnsafeRecordId warning that contains the form name. This warning indicates that QBL cannot ensure the record ID will point to the same record as specified, and cannot verify whether the record ID is real or not.
Example:
"UnsafeRecordId: in $Table_Flower_Care some form rules reference specific record IDs.
QBL populated the form rule, but did not populate the record IDs.
Define which records to reference by adjusting the form rules in Quickbase for these
forms: $Form_Flower_Care_Main_Form at Line 1730, Column 8"