Does Key Exist in JSON Object

This block uses JSON data format. If you don't know what JSON is take a look at What is JSON?

The JSON add to object task block consists of an input and True and False outputs.

If the input to the JSON Does Key exist is triggered the block will check if the key entered is in the JSON object entered. If the key exists the True output will be triggered else the False object will be triggered.

Examples

Here is a simple example of a mission that uses a JSON Does Key Exist in Object. This example checks if the key "first" exists in the JSON array. If it exists it will trigger the mission log block to log "Exists" to the mission log. If it doesn't exist it will log "Does not Exist" to the mission log.

Copy / Settings / Docs

Each task block has three buttons named Copy, Settings, and Help.

• Copy: This will duplicate the task block with all the current settings.
• Settings: Settings will show a dialog that allows some added configuration for the block
  • Note: This allows you to add a text note for the current block. This note will appear in the log file if the Block Loggin option is enabled.
  • Transition Out Time: Each block can specify a delay in milliseconds that it will wait after an output trigger is activated. This feature is generally not used but is avilable for more granular flow control of the mission if needed.
  • Block Logging: If this is enabled then the internal logging of the block is turned on and will be sent to the mission log. Each block has different amounts of internal logging which can make mission logs become large in some cases. Users generally do not enable this feature because of the limits to data storage.