Firebase Auth, Firestore & Storage (plugin)
  • 🚀Getting Started
  • Setup
    • Create a Firebase Project
    • Get Firebase access credentials
    • Offline Support
    • Secure your credentials and data
      • Restrict your api-key to your domain
      • Security Rules on Firebase
  • Plugin Elements
    • 🛠️About elements
    • 💾Data Schemas
    • Firebase Auth (Current User)
    • Firestore Data List
      • Firebase Geohash
      • Firestore Data (legacy)
    • Firestore Data Extractor
    • Firestore Data Single
    • Firestore Data Aggregation
    • Firestore Data Processor
    • Firebase Storage Upload Button
    • Firebase Action Listener
    • Firebase Dropdown Processor
  • Plugin Front-end Actions
    • 💻About front-end actions
    • 💾Field types table
    • Firestore
      • Create a new document
      • Update a document
      • Delete a document
      • Update a list of documents
      • Delete a list of documents
      • Batch Operations
        • Batch Operation Constructor
        • Batch Operation Commit
    • Firebase Auth
      • Sign the User Up
      • Log the User In
      • Log the User In with Google
      • Log the User In with Facebook
      • Log the User In with GitHub
      • Log the User Out
      • Update User's Profile
      • Update User's Password
      • Update User's Email
      • Send password reset email
        • Handle reset password code
      • Send verification email
        • Handle verify email code
      • Delete current user
    • Firebase Storage
      • Upload file base64
      • Delete uploaded file
  • Plugin Back-end Actions
    • ☁️About backend actions
    • Firestore Backend
      • Get a list of documents
      • Get a single document
      • Count a list of documents
      • Create a new document
      • Update a document
      • Delete a document
      • Update a list of documents
      • Delete a list of documents
    • Firebase Auth Backend
      • Create an account for someone else
      • Update another user's profile info
      • Delete a user account
      • Generate email confirmation link
      • Generate password reset link
      • Set user roles
Powered by GitBook
On this page
  • Inputs and Settings
  • Document ID
  • Collection
  • Trigger ID (optional)
  • Fields
  • Field Types
  • Triggered events
  • Stored values on the listener
  • Updated Document ID
  • Error Message
  1. Plugin Front-end Actions
  2. Firestore

Update a document

PreviousCreate a new documentNextDelete a document

Last updated 11 months ago

This action allows you to edit/update document in a Firestore collection.

You still don't need to have the collection or "table schema" pre-determined. You can create any fields you'd like during document updates.


Inputs and Settings

Document ID

The ID of the document you want to update.

Collection

The name or ID of the collection the document you want to update is stored in.

Trigger ID (optional)

If left blank, all listeners on the page with blank ID's will be triggered at the same time, so we suggest to always define a Trigger ID.

Fields

Field Types

For each key/value pair you define and provide a value on the Fields list, you must provide the same key, but with the type of the value, on the Field Types input. That allows the plugin to turn the texts being fed into the plugin into corresponding values on the JSON structure sent to Firestore.

If the number of Fields and Field Types don't match, the action will result in an error.


Triggered events

  • Document Updated (if the action was successful)

  • Error in Action (if an error occurs)


Stored values on the listener

Updated Document ID

The ID of the document updated by the action.

Error Message

If an error occurs, you can check its details on this state on the action listener.

This will link the action with a of the same ID.

When the function finishes running, it will trigger the event, storing the on the listener's state.

The same way as on the you must inform which fields you want to update, in JSON format. This input allows you to set as many fields as you want.

For each field you must specify the "key" and the "value" that will be stored on it. For instance, you might want to invert the value of the "done" field in a task on our , when the check icon is clicked. You'd need to define the "key" = "done" and the "value" = "true" or "false".

See the to see which types are currently supported by the plugin and how to define them.

Those events are triggered by an with the same ID as the provided on the action.

Action Listener
Document Updated
Updated Document ID
Create New Document action
task manager sample app
field types table
Action Listener
Trigger ID
The "done" field is set to the opposite of the current tasks "done" value. If "true", it'll be updated to "false", and vice versa