The collections associated with an app can be viewed by selecting the Data Browser tab in the Cloud Management section of the Studio.

This screen has two controls located at the top of the collection list

These buttons

Clicking on the button to add a collection prompts you to enter the collection name. Click on the Create button to create the collection.

To view the data stored in a collection simply click on one of the collections listed in the Data Browser. This view shows the data accociated with the collection.

At the top of the screen are the main listing functions

These buttons allow you to

{
   "title":"",
   "author":{
       "name":"John"
   }
}

Editing data in the Data Browser can be done using either the Inline or Advanced Editor

Data is exported from the Data Browser by using the 'Export' dropdown menu. Three formats are available:

After clicking on the export button for your chosen format, a .zip file will be downloaded. The contents of this is your data.

To export all collections contained within your app, use the 'Export' dropdown in the toolbar on the collection listing screen. To export an individual collection’s data, use the 'Export' dropdown from within that collection’s data listing.

Exporting data should give you a pretty good idea of the formats expected for import. This schema for each format is documented in more detail below.

You can import data into the data browser by clicking the 'Import' button on the collection listing screen. Supported formats are:

Every file corresponds to a collection to be imported. The name of that file corresponds to the collection name your data will be imported to.
If a collection does not already exist, we will create it. If the collection already exists, imported documents are appended to the existing contents.

[
  {
    "name":"plums",
    "price":2.99,
    "quantity":45,
    "onSale":true,
    "_id":"53767254db8fc14837000002"
  },
  {
    "name":"pears",
    "price":2.5,
    "quantity":20,
    "onSale":true,
    "_id":"53767254db8fc14837000003"
  }
]

name,price,quantity,onSale,_id
"plums",2.99,45,true,53767254db8fc14837000002
"pears",2.5,20,true,53767254db8fc14837000003

{ "name" : "plums", "price" : 2.99, "quantity" : 45, "onSale" : true, "_id" :   ObjectId( "53767254db8fc14837000002" ) }
{ "name" : "pears", "price" : 2.5, "quantity" : 20, "onSale" : true, "_id" :  ObjectId( "53767254db8fc14837000003" ) }
2 objects found

To start a new export job, enter the following command:

fhc appdata export start --appId=<APP_ID> --envId=<ENV_ID> [--stopApp=[y/n>]]

Once done, you receive a prompt asking whether you want to stop the app during data export.

To skip the prompt after running the command (for example, when scripting fhc), provide the optional --stopApp flag with the command before running.

If another export job is already running for the same app in the same environment, the start command will exit without performing any action.

Once the job starts, the command line tool prints out the following status command with all the relevant fields already filled in.

fhc appdata export status --appId=<APP_ID> --envId=<ENV_ID> --jobId=<JOB_ID> [--interval=<MILLISECONDS>]

To query the status of an export job, copy and paste this command into the shell.

To keep the command running and periodically reporting the job status, include the optional --interval flag and specify the interval at which the status of the job is to be queried.

Once the job is finished, the status command returns the job status as complete.

To download your exported data once the job is finished, run the following download command:

fhc appdata export download --appId=<APP_ID> --envId=<ENV_ID> --jobId=<JOB_ID> --file=<FILENAME>

To start a new import job, enter the following command:

fhc appdata import start --appId=<APP_ID> --envId=<ENV_ID> --path=<FILE_PATH>

Upon execution, the command starts uploading the provided file, and keeps running without printing any messages until the upload is finished. Once the upload is finished, the command exits and the import job starts.

If another import job is already running for the same app in the same environment, the start command exits without performing any action.

Once the job starts, the command line tool prints out the following status command with all the relevant fields already filled in.

fhc appdata import status --appId=<APP_ID> --envId=<ENV_ID> --jobId=<JOB_ID> [--interval=<MILLISECONDS>]

To query the status of an import job, copy and paste this command into the shell.

To keep the command running and periodically reporting the job status, include the optional --interval flag and specify the interval at which the status of the job is to be queried.

Once the job is finished, the status command returns the job status as complete.