- Cómo empezar a usar Airtable
- Introducción a los aspectos básicos de Airtable
- Cómo comunicarse con el equipo de soporte de Airtable
- Pantalla de inicio de Airtable
- Glosario de terminología de Airtable
- Airtable technical requirements
- Diferencias entre las funciones de Airtable para escritorio y para móvil
- Atajos de teclado de Airtable
- Cómo usar Markdown en Airtable
- Adding descriptions in Airtable
- Finding Airtable IDs
- Automatizaciones de Airtable
- Descripción general de automatizaciones
- Guías de automatizaciones
- Guías de automatizaciones integradas
- Guías de automatizaciones en Airtable
- Linking existing records using automations
- Conditional groups of automation actions
- Repeating groups of Airtable automation actions
- Creating recurring records using automations
- How to delay Airtable automation runs
- Prevent automations from triggering by mistake
- Use automations to timestamp status updates
- Desencadenantes de automatizaciones
- Desencadenantes de Airtable
- Airtable automation trigger: When record matches conditions
- Airtable automation trigger: When a form is submitted
- Airtable automation trigger: When record created
- Desencadenante de automatización de Airtable: cuando se actualiza un registro
- Airtable automation trigger: When record enters view
- Desencadenante de automatización de Airtable: a una hora programada
- Airtable automation trigger: When webhook received
- Airtable automation trigger: When a button is clicked
- Airtable automation trigger: When email received
- Desencadenantes integrados
- Desencadenantes de Airtable
- Acciones de automatización
- Acciones en Airtable
- Acción de automatización de Airtable: enviar correo electrónico
- Airtable automation action: Create record
- Airtable automation action: Update record
- Airtable automation action: Find records
- Airtable automation action: Sort list
- Acción de automatización de Airtable: ejecutar un script
- Airtable automation action: Generate with AI
- Acciones integradas
- Airtable automation actions: Slack
- Airtable automation actions: Google Workspace
- Airtable automation action: Send MS Teams message
- Airtable automation actions: Outlook
- Airtable automation actions: Jira Cloud
- Airtable automation actions: Jira Server / Data Center
- Airtable automation actions: Salesforce
- Airtable automation action: Create post in Facebook Pages
- Airtable automation actions: GitHub Issues
- Airtable automation action: Hootsuite post
- Airtable automation action: Send Twilio SMS
- Acciones en Airtable
- Bases de Airtable
- Using Airtable Cobuilder
- Descripción general de las bases de Airtable
- Creating and duplicating bases in Airtable
- Structuring your Airtable bases effectively
- Moving Airtable bases between workspaces
- Tables in Airtable
- Crear enlaces para compartir bases de Airtable
- Importing third-party data into Airtable
- Uso de las perspectivas
- Troubleshooting Airtable base performance
- Versiones beta de Airtable
- Colaboración en Airtable
- Asistencia de Airtable Enterprise
- Información general
- External badging in Airtable
- Creating and using Airtable components
- Ask an Expert beta overview
- Data residency at Airtable
- Descripción general de los grupos de usuarios en Airtable
- API de Enterprise de Airtable
- Creating and managing data retention policies in Airtable
- eDiscovery APIs in Airtable
- Airtable and data loss prevention
- Acceder a los registros de auditoría de Enterprise en Airtable
- Configuración de Jira Server/Data Center para conectarse con Airtable
- Panel de Administración de Enterprise
- Descripción general del panel de administración de Enterprise
- Usuarios: panel de administración de Enterprise en Airtable
- Detalles del usuario en el panel de administración de Airtable
- Grupos: panel de administración de Airtable
- Espacios de trabajos: panel de administración de Enterprise de Airtable
- Bases: panel de administración de Enterprise en Airtable
- Interfaces: Panel de administración de Enterprise en Airtable
- Data sets - Airtable admin panel
- Managed apps - Airtable admin panel
- Components - Airtable admin panel
- Informes: panel de administración de Enterprise en Airtable
- Airtable admin panel settings
- Guía práctica de Enterprise
- Gestionar a los admins de Enterprise en el panel de administración
- Uso de organizaciones
- Organizational branding for apps in Airtable
- Enterprise Hub in Airtable
- Enterprise Hub : Org unit assignment with user groups
- Desactivar, retirar el acceso y reactivar usuarios desde el panel de administración
- Gestionar el acceso de usuario a espacios de trabajo y bases
- Airtable Enterprise Key Management
- Custom terms of use
- SSO en Enterprise
- Información general
- Extensiones de Airtable
- Descripción general de las extensiones
- Extensiones por Airtable
- Extensiones integradas
- Campos de Airtable
- Descripción general de los campos
- Archivo adjunto
- Campos basados en fecha
- Fórmula
- Empezar a usar fórmulas
- Fundamentos de fórmulas
- Soluciones frecuentes: principiante
- Soluciones habituales: intermedias
- Soluciones habituales: avanzado
- Campo de texto largo
- Campos de registros vinculados
- Campos con números
- Otros campos
- Campos de compilación, búsqueda y recuento
- Campos de selección y colaborador
- Integración con Airtable
- API
- Getting started with Airtable's Web API
- Crear tokens de acceso personal
- Airtable Webhooks API Overview
- Service accounts overview
- API web de Airtable: usar filterByFormula o parámetros para ordenar
- Airtable API Deprecation Guidelines
- Airtable API: Common troubleshooting
- Managing API call limits in Airtable
- Enforcement of URL length limit for Web API requests
- Servicios de integración
- Third-party integrations via OAuth overview
- Troubleshooting disconnected OAuth integrations in Airtable
- Options for integrating with Airtable
- Third-party integrations - Common troubleshooting
- Low-code integrations - Common troubleshooting
- Integrating Airtable with external calendar applications
- Visualizing records from Airtable in Tableau
- Visualizing Airtable records in Microsoft Power BI & Power Query
- Integrating HubSpot with Airtable
- Using Zapier to integrate Airtable with other services
- Using Zapier's Multi-Step Zaps to find and update records
- Using IFTTT to integrate Airtable with other services
- Integrating with AWS Lambda & DynamoDB
- Herramientas para desarrolladores
- API
- Diseñador de Interfaces de Airtable
- Descripción general
- Diseños de página
- Elementos
- Adding and removing elements in interfaces
- Adding layouts to interfaces
- Formatting elements in interfaces
- Interface element: Button
- Interface element: Calendar
- Interface element: Chart
- Interface element: Filter
- Interface element: Gallery
- Interface element: Grid
- Interface element: Kanban
- Interface element: Number
- Interface element: Record picker
- Interface element: Text
- Interface element: Timeline
- Aprendizaje y recursos
- Gestión de Airtable
- Política de Airtable
- Registros de Airtable
- Sincronización de Airtable
- Vistas de Airtable
- Espacios de trabajo de Airtable
- 18 Dec 2023
- 4 Minutos para leer
- Impresión
- Compartir
- OscuroLigero
- PDF
Conditionally displaying missing field values in Airtable
- Actualizado en 18 Dec 2023
- 4 Minutos para leer
- Impresión
- Compartir
- OscuroLigero
- PDF
This article covers how to use IF, AND, and FIND functions to streamline your team's and organization's work.
Introduction
All plan types | |
Platform(s) | Web/Browser, Mac app, and Windows app |
Related reading |
Conditionally displaying missing field values
NOTE
The IF, AND, and FIND functions allow you to create formulas that will conditionally keep track missing base information.
Example base used in this article
Example use case
To start, we'll be using an applicant tracking base as an example scenario. This simple base is setup to track each stage an applicant goes through during a company hiring process.
Example requirements
The recruiting team needs to make sure a number of tasks are completed for each candidate during each stage of the process. These tasks correspond to the checkboxes in our table:
The candidate passing the interview (Interviewer Pass)
Updating the team (Team Update)
The Recruiter following up with the candidate (Recruiter Follow Up)
Moving the candidate to the next stage (Move Stage)
Optionally, if the candidate is applying for a management role, updating the department director (Director Update)
For their workflow, the recruiting team would like a single field to show a list of any tasks that are remaining for each candidate in each stage. They want to use this field to send an automated update every day to their team's Slack channel for more visibility into the recruiting process.
Building formulas
Starting with the logic needed to accomplish this, here's the requirements written out plainly:
If any of the fields above are blank, show the task for that field as missing.
If the candidate is applying for a management role, also include the director update field.
Display the results of checking each field in a single formula field, ideally with each missing task separated by a comma, and separated by a line break.
An IF statement is needed to check each of these fields, and will be structured like this:
IF(
{Interviewer Pass}=BLANK(),
"Interviewer Pass"
)
However, we'll need to string five conditional statements together in the formula field. We'll also need to build in comma separation and line breaks. Here's what that should look like with just two out of the five sets of statements we'll need.
Let's breakdown what's going on in the formula above:
This checks if the field is empty (in this case, unchecked)
Display this text if the field is empty
Adds a comma separator
", "
Adds a line break
"\n"
Allows a separator so the next conditional statement can be added
Stringing conditional statements together
When you add on the other three sets of conditional statements, the entire formula will look like this:
IF({Interviewer Pass}=BLANK(), "Interviewer Pass" & ", " & "\n")
&
IF({Team Update}=BLANK(), "Team Update" & ", " & "\n")
&
IF({Recruiter Follow Up}=BLANK(), "Recruiter Follow Up" & ", " & "\n")
&
IF({Move Stage}=BLANK(),"Move Stage" & ", " & "\n")
&
IF(
AND(
FIND("Manager", Role),
{Director Update}=BLANK()
),
"Director Update"
)
Notice that for the last statement there are two additional functions - AND()
and FIND()
- that allow for a conditional check to see if the role is a management role, and if it is, add on a check to see if the {Director Update} field is checked.
Final result
For the final result, we can see that every field that is checked off will be removed from the running list of missing tasks, until they're all complete.
Line break alternatives
With the added line breaks, each task will appear on its own line. A benefit of the formula string used for this approach is that there aren't an empty lines between tasks shown when the row height is expanded.
This is an alternative approach to use of "\n", and for the sake of example it's helpful to see how the typical approach to line breaks would look in this scenario. As a quick review:
The typical line break approach uses this string to force line breaks between functions in a formula:
& "\n" &
. This string would go after each formula function where you want to insert a line break.The alternate approach (used in this article) uses this modified string:
& "\n"
). This string goes within each function, making the line break part of the conditional display of text (in the IF statement).
The result of this alternate approach is that only a line break is added if the condition is met - in this case, if a task is missing.
For reference, here's how the full formula used above would look with the typical line break approach:
IF(
{Interviewer Pass}=BLANK(),
"Interviewer Pass, ")
& "\n" &
IF(
{Team Update}=BLANK(),
"Team Update, ")
& "\n" &
IF(
{Recruiter Follow Up}=BLANK(),
"Recruiter Follow Up, ")
& "\n" &
IF(
{Move Stage}=BLANK(),
"Move Stage, ")
& "\n" &
IF(
AND(
FIND("Manager", Role),
{Director Update}=BLANK()
),
"Director Update"
)
And here's an example of what the result would be; notice the line breaks between tasks, which isn't ideal for this scenario (and takes up unnecessary visual space).