Error messages and warnings
The Buzzy Figma plugin and the debug/preview mode of your app provide warnings and error messages if something isn’t quite right. Here’s a list of the messages and what they might mean.
Filter fields must be in a filter element
What it means: Certain Buzzy field types need to be nested inside a wrapping element like form, view or filter.
How to fix it: You need to wrap the filter field in a filter element.
Insert and edit fields must be in a form component
What it means: Certain Buzzy field types need to be nested inside a wrapping element like form, view or filter.
How to fix it: You need to wrap ‘insert’ and ‘edit’ mode fields in a form element.
Insert mode fields can only be used on capture mode form
What it means: Your field is in ‘insert’ mode, but not wrapped in a form element in ‘capture’ mode.
How to fix it: You need to wrap ‘insert’ mode fields in the ‘capture’ mode layout of a form element.
Field must be in ‘insert’ mode on an capture mode form
What it means: Your field is in a mode other than ‘insert’, but nested inside a form element in ‘capture’ mode.
How to fix it: All of the fields inside a the ‘capture’ mode layout of a form must be in ‘insert’ mode.
No row data is available for the field to show; ensure a row is being passed to the screen
What it means: No data table row was available for the field to read data from. This typically means an action that navigated to this screen was not set up to send data table row data.
How to fix it: Make sure the relevant navigation action is set to ‘pass current data’ to this target screen.
Field does not exist in the current row; ensure the correct field has been selected
What it means: The available data table row did not have the field on it. This typically means either the wrong field was selected, or there is an action that navigated to the screen using a row from the wrong data table view.
How to fix it: Make sure this field exists in the data table you are currently targeting, and that when navigating to this screen that you are passing data from the correct data table to this screen.
Field does not match the form data table (microapp)
What it means: The specified field is not from the same data table as defined on its wrapping form element. A field always belongs to a single parent data table. In this case, you appear to be referring to a field that is not in the data table that the form refers to.
How to fix it: Make sure your field is in the data table you have created your form for, or your form refers to the data table which contains this field.
Field does not match the filter data table (microapp)
What it means: The specified field is not from the same data table defined on the wrapping filter element. A field always belongs to a single parent data table. In this case, you appear to be referring to a field that is not in the data table that your filter refers to.
How to fix it: Make sure your field is in the data table you are trying to filter, or your filter applies to the data table which contains this field.
JSONATA error: (specific error message)
What it means: The JSONATA formula has an error in it as specified in the message.
How to fix it: Make sure your JSONATA formula uses the correct syntax. See our docs and jsonata.org for help on formulas. Use backticks for labels with spaces & special characters.