Buzzy Documentation
  • Welcome to Buzzy
  • Getting Started with Buzzy
    • Getting Started Guide
      • 1. Starting with Buzzy AI
      • 2. The Buzzy Workspace
      • 3. Create a new app
      • 4. Preview and edit your app
      • 5. Manage your app
      • 6. Import your app to Figma
      • 7. Using Buzzy with Figma
      • 8. The Buzzy Figma plugin
      • 9. Creating a simple app
      • 10. Screens and navigation
      • 11. Forms, fields and data
      • 12. Data-driven menus & content
      • 13. Data edit and delete
      • 14. Search, sort and filter
      • 15. User login and registration
    • Buzzy AI or Figma first?
  • Working with Buzzy
    • Buzzy AI
      • About Buzzy AI
      • Kickstart with AI
      • Enhance with Figma
      • Extend with Code
      • Example prompts
      • Tips
      • Troubleshooting Buzzy AI
      • AI tokens and pricing
    • Buzzy for Figma
      • About Buzzy for Figma
      • Learning Figma
      • Creating a new app directly in Figma
        • Step by step version
      • Automarkup
      • Responsive layouts
      • Responsive layout checklist
      • Overflow and scrolling
      • Forms and fields
      • Logging users in to your app
      • Theming
      • Troubleshooting Buzzy for Figma
      • Plugin error messages
    • Buzzy Deployment & App Stores
      • Setting up your custom Buzzy app
      • Connecting your own server
      • Apple & Google App Stores
    • Buzzy Marketplace
      • Buzzy Accreditation
    • Buzzy Project Guide
    • Buzzy App Examples
      • Buzzy Templates
      • AI-Powered Chat App
      • AI-Powered Custom T-Shirt App
      • AI-Powered Strategy App
      • AI-Powered Stock Portfolio App
      • Golf Course Finder
      • Personal Finance App with Figma AI
    • FAQs
  • The building blocks
    • Datatables, Fields & Data
      • Introduction to Fields
      • Basic Fields
        • Text
        • Number
        • Date
        • Location
        • Toggle
        • Checkboxes
        • Checklist
        • Selectlist
        • Rating
        • Attachments
        • Images
        • Signature
        • Audio Recording
        • Embedded Link
      • Advanced Fields
        • Formula
        • Sub tables
        • Linked Table field
        • Button
        • Teams
        • Payment
        • Notification
        • Event
        • User Vote
      • Display Fields
        • Header
        • Display Text
        • Image
        • Divider
      • Metadata Fields
        • Author Name
        • Author Phone
        • Submitted
      • Filter Controls
        • Viewers
        • Tags
        • Condition
      • External Fields
        • IBM Connections File
        • Box File
      • Sort Fields
      • Formulas
      • Datatable to Datatable Relationships
      • Security and Access Control
      • Displaying a field based on the values of other fields
      • Hiding a field based on role using a display formula
      • Importing data from a text file
      • Importing data from a URL
      • Import data from Datatable
      • Export data using Chrome
      • Export data in Browser
      • Export data using Safari
      • Datatable Field Type - Cheat Sheet
      • Troubleshooting Fields & Data
    • Code widget (custom code)
      • Code Widget Fields - Advanced Guide
      • New Async API + React HTML Components
      • Examples
        • Image Galley Slideshow
        • Ratings Average and Distribution
        • Event Locations Map
    • Analytics
  • Troubleshooting
    • App Error Codes
      • Action Error
      • App Not Found
      • Component Missing
      • Component Not Set
      • Component Settings Error
      • Datatable Not Found
      • Datatable Not Set
      • Field Not Found
      • Field Not Set
      • No App Selected
      • No Context Name
      • No Screens Found
      • Runtime Exception
      • Screen Not Found
      • Screen Not Set
    • Troubleshooting Buzzy AI
    • Troubleshooting Figma
  • REST API
    • Buzzy REST API
      • Integrating 3rd party applications
      • REST API
        • login
        • createappwithprompt
        • MicroApp Data Operations
          • microappdata
          • microappdata/row
          • insertmicroapprow
          • updatemicroapprow
          • removemicroapprow
          • microappchild
        • User & Organization Operations
          • userid
          • insertteammembers
          • teammembers
          • insertorganization
          • insertteam
        • enforceteammembership
      • Node.js API Client
      • Datatable Rules
      • Datatabledata Tutorial
      • Integrating with Mailchimp
      • Python Access Datatable
  • Advanced Deployment Settings
    • Installation
      • Pre-installation Planning
      • Deployment
        • Introduction to deployment
        • Minikube install guide
        • AWS ECS Fargate install guide
        • HCL Connections install guide
        • Azure AKS install guide
        • Windows container install guide
      • Buzzy settings
      • Whitelabelling Buzzy
      • Certificates
      • Release Management
    • Performance and Reliability
    • Security
      • Platform
      • Users and Roles
      • Datatables
      • Audit Trail
Powered by GitBook
On this page
  • Filter fields must be in a filter element
  • Insert and edit fields must be in a form component
  • Insert mode fields can only be used on capture mode form
  • Field must be in ‘insert’ mode on an capture mode form
  • No row data is available for the field to show; ensure a row is being passed to the screen
  • Field does not exist in the current row; ensure the correct field has been selected
  • Field does not match the form data table (microapp)
  • Field does not match the filter data table (microapp)
  • JSONATA error: (specific error message)
  1. Working with Buzzy
  2. Buzzy for Figma

Plugin error messages

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.


PreviousTroubleshooting Buzzy for FigmaNextBuzzy Deployment & App Stores

Last updated 6 months ago

How to fix it: Make sure your JSONATA formula uses the correct syntax. See our and for help on formulas. Use backticks for labels with spaces & special characters.

docs
jsonata.org