How to Get Selectors and Field Codes

  • Updated

Quick Take

  • A field/section "Name" is what is displayed in Filevine and these are editable. The can have spaces and often look something like "My Field Name"
  • A field/selection "Selector" is the unchangeable value given to the section/field/widget when it was created. In the Filevine Customs Editor, these are seen in grey text under the "name," cannot have spaces and often look something like "myFieldName". 
  • A "field code" combines a "section selector" and a "field selector" between {{ }} to point to a specific field in a Filevine project type. They look like {{mySectionName.myFieldName}}.


It's important to understand how to extract selectors and field codes, as they work as the primary inputs to the bot, and they must be added to the configuration project of each bot or bot’s item. Depending on the type of field or information that the bot needs from the fields or widgets, selectors or field codes will be used; however, below, you will learn how to extract both: 

1. Go to the Customs Editor section in Advanced to access the sections of the Project Template where you will use the bot, following the following steps:

    1. Go to the menu in the top left-hand corner of Filevine and select "Advanced."

    2. Select "Customs Editor" from the left-hand menu within "Advanced."

    3. Choose the Project Type where you will use the bot.

2. Click on the section where you need to extract selectors or field codes.

3. Extract the selectors or field codes according to the following:

  1. If you need the section selector, extract it from the Section Selector field, as shown in the following image:

  2. If you need the selector or code of a field:

    1. Click on the field from the Custom Fields/Widgets section from which you need to extract the selector or field code. 

    2. Copy the value from the Field Selector field if you need the selector as shown in the following image:

  1. Copy the value below the Field Selector field if you need the code field.

Was this article helpful?

0 out of 0 found this helpful



Article is closed for comments.