---
title: "Configuration Editor"
canonical: "https://help.fieldbuddy.com/space/FBDOCS/3094808809/Configuration%20Editor"
format: markdown
---
## What is Configuration Editor

Configuration Editor is a tool, that allows to view and change configuration(s) for FieldBuddy Swift, as well as manage assignments. It can be opened via custom Tab or using [Configuration Panel](https://upperdeck.atlassian.net/wiki/spaces/FBDOCS/pages/5365268532)

> ℹ️ Configuration editor supports up to 10 active or draft configurations in total at the moment

Below is the sample screenshot of Configuration Editor. 

![image](media://7f35597c-6237-44f1-8207-78435e847fce)

## What is FieldBuddy Swift Configuration

tl;dr

1. Contains parameters for Mobile Application (aka Screens) and dataset to be shown in Mobile Application (aka Briefcase)
2. Format of Configuration is JSON. Check for an example in screenshot above
3. Configuration may be in Draft Status. Then it is possible to change that, but not possible to assign that to User
4. Configuration in Draft status may be changed to status Active. Then it is impossible to change  that, but it is possible to assign that for Usage
5. Configuration can be assigned to User. Assignment may be in status Assigned or Current. If you assign Config to user, it will be became current as soon as user relogin to FieldBuddy Swift
6. Configuration can not be deleted if it is Current at least for one user. To delete it, reassign users(s) to new configuration and ensure that it became current for them
7. Configuration can be Cloned and Deleted
8. Configuration can be Validated (very basic integrity validation for Screens and Briefcase)
9. Normal flow to change configuration for "real life"
  1. Clone existing configuration that needs to be adjusted
  2. Perform necessary adjustments
  3. Activate configuration
  4. Reassign test user to newly activated config
  5. Perform basic testing of it. In case of issues – go to step a., otherwise go next
  6. Reassign more users to new configuration. Enjoy

## How to Use Configuration Editor

Configuration Editor consists from 2 parts – overview of all available configurations (1) and view for current one (2)

![image](media://c952575c-0952-4e1d-8a33-9db1ca8b3aec)

### Overview of all configurations

In left panel you can see list of all available configurations. It shows name of it, (I) sign if there are any notes, status (3) and to how much users it is assigned or current (4)

At the left (5) you can see a small dropdown with list of all available actions – like Clone, Activate or Delete. 

Important notes:

1. You can  delete only unused configuration
2. You can activate only draft configuration
3. You can clone any configuration
4. You can assign only active configuration

### Single Configuration Details

Has 4 tabs

1. Configuration – allows to change screens and other options for mobile applications
2. Briefcase – allows to change dataset for mobile application
3. Assignments – allows to assign users for a config
4. Notes – shows who did recent change for config, and/or some custom notes if needed.

### Validation

Validation allows to perform basic :warning: check over Screens and Briefcase parts.

It check briefcase first, and if it is valid – checks Screens.

#### What is checked for a Briefcase

1. if it is valid JSON (as JSON Structure)
2. if it has valid structure (all required fields, like Target, Fields)
3. if it has valid sObjects referenced
4. If it has valid fields for sObject, which is mentioned
5. If it has valid Filter conditions (like RefreshCondition and Condition)

#### What is not checked for a Briefcase

1. If Reference Field is valid.

#### What is checked for a Screens

1. If it is a valid JSON (as JSON Data Structure)
2. If it has Screens entry (in a root – Screens)
3. If it has a DataBinding
  1. Valid table (as sObject)
  2. Valid field (as API field Name)
  3. If those are referenced in a Briefcase
4. If it is a OrderBy or GroupBy
  1. Valid table (as sObject)
  2. Valid field (as API field Name)

That is pretty much it about validation


## What to do if Configuration Editor does not load?  


It could be that configuration editor stuck with grey screen and does not load. That might happen if there are more then 10 of active or draft configurations, and in order to proceed, it is necessary to put status of some of those to “archived” via Configuration record detail page (Configurations tab)