InformationTitleLeanData Scheduling - Data Table Based Routing GuideURL NameLeanData-Scheduling-Data-Table-Based-Routing-GuideStep-by-StepContents: OverviewUse CasesPrerequisitesHow Data Table Based Routing Works in BookItSetting Up a Data Table for BookItBookIt Output ColumnsAdding the Data Table Node to a BookIt GraphConfiguring the Data Table NodeAdvanced SettingsRouting Prospects Away from BookingStamping Field Values with Output to VariablesSharing a Data Table with OrchestrationMonitoringConsiderationsFAQsSummary Overview Data Table Based Routing (DTBR) lets you route meetings from a spreadsheet-style Data Table instead of a long chain of decision, territory, and branch nodes. Each row of the table holds both the set of criteria and the corresponding output when a prospect matches them. When a prospect or record reaches the Data Table node in a BookIt for Forms or BookIt Handoff graph, LeanData compares it with the table's rows and uses the first row that matches. In LeanData Scheduling, a matched row can do more than populate a set of values. It tells BookIt who hosts the meeting, which additional hosts to invite, which meeting type or types to offer, and, in BookIt Handoff, which parts of the suggestion the scheduler can't change. Because the routing logic lives in the table, anyone on your team can read it and update it without rebuilding the graph. The Data Table node runs in one of two modes: Schedule a meeting: Books the meeting (BookIt for Forms) or suggests it to the scheduler (BookIt Handoff) using the host and meeting type from the matched row.Output to variables: Stores the matched row's values as variables for later nodes in the graph. No meeting is scheduled. Scheduling and Orchestration share the same Data Tables. A table you already use to route records in Orchestration only needs the BookIt-specific output columns added before you can use it to schedule meetings. This article covers the parts of Data Table Based Routing that are specific to Scheduling. For the general steps to create, version, and manage Data Tables, and for the operators and DateTime formulas you can use in input cells, see the Routing - Data Table Based Routing Guide. Key Terms Data Table: A table of input columns and output columns, built in Data Table Management.Input column: A column whose cells are compared with values from the form submission, the matched Salesforce record, or graph variables.Output column: A column whose cells hold the result for that row, such as the main host, the meeting type, or a value to store in a variable.Main Host: The BookIt user or round robin pool that hosts the meeting. In a Data Table, the main host comes from an Owner/Main Host column.[NONE]: A special cell value. In the Owner/Main Host column, it marks a row that matches but should not be scheduled. Example: Connie is the LeanData Admin for OnPoint Communications. Her BookIt for Forms graph uses a long chain of territory and decision nodes to send demo requests to the right rep based on country, company size, and product interest. She replaces that chain with a single Data Table node. Each row lists a combination of those three values, the rep or pool that should host, and the meeting type to book. When OnPoint reorganizes its territories, Connie edits the table and activates a new version instead of rebuilding the graph. Use Cases Simplify large BookIt graphs. Replace chains of decision, territory, and branch nodes with one table that lists every routing combination as a row.Book a different meeting type for each segment. Set the meeting type per row, for example a demo in the prospect's language for each country, or a shorter intro call for smaller companies.Reuse the tables you already route with. Use the same Data Table that assigns Leads in Orchestration to schedule meetings in BookIt, so routing and scheduling follow the same rules.Build group meetings from the table. Add a solutions engineer as a required additional host on enterprise rows, and a manager as an optional host who is invited but doesn't need to be free.Turn away prospects you don't want to meet with. Set the main host to [NONE] on rows for student email domains, competitors, or existing customers, and send those prospects to a web page instead of a calendar.Control BookIt Handoff suggestions. Lock the suggested main host or meeting type on certain rows, such as strategic accounts, so the scheduler can't change them.Stamp values on records from Routing Links. Look up values such as segment or region with a Data Table, then write them to the Lead or Contact with an Update Record or Create Record node. Prerequisites LeanData version 10.x or later.BookIt for Forms, BookIt Handoff, or both.Every user named as a host in the table must be authorized for BookIt and have access to the BookIt product the graph uses. For details, see Authorizing LeanData BookIt (for End Users) and LeanData BookIt - BookIt Permissions & Access Levels.Any meeting types and round robin pools you reference in the table must already exist in Scheduling. How Data Table Based Routing Works in BookIt A prospect submits a form (BookIt for Forms), or a scheduler starts a booking from a Salesforce record (BookIt Handoff), and the graph reaches the Data Table node.The node reads the value mapped to each input column and compares those values with the rows of the table's active version, from top to bottom. A row matches only when every mapped input column matches. The first matching row is used.What happens next depends on the node's mode and the matched row: Schedule a meeting: LeanData books or suggests the meeting with the row's main host, additional hosts, meeting type, and locks. If the row's main host is [NONE], the prospect follows the Do Not Schedule edge instead.Output to variables: The row's regular output values are stored in variables, and the graph continues on the Next Node edge. If no row matches, the prospect follows the Data Table Rows Not Met edge. The node always reads the table's active version. When you activate a different version, every graph that uses the table, both in Scheduling and in Orchestration, picks up the change right away without being redeployed. Input Sources The values you can compare with input columns depend on the product: BookIt for Forms: Form submission fields, fields on the matched Salesforce record, and graph variables.BookIt Handoff: Fields on the Salesforce record the meeting is booked from, and graph variables. BookIt Handoff has no form submission. Setting Up a Data Table for BookIt Opening Data Table Management In the LeanData app, go to BookIt > Data Table Management. This page shows the same Data Tables as Routing > Data Table Management. There is one set of tables, so a table you create or edit from either page is available to both Orchestration and BookIt graphs. Creating a Data Table On the Data Table Management page, click Create Data Table.Enter a Data Table Name and a Version Name.Choose whether to build the table in LeanData or upload a CSV file.Set up your columns. For each column, enter a name, choose Input or Output, and select a data type. Add the BookIt output columns described in BookIt Output Columns below for the meeting details you want the table to control. Fill in your rows and click Save. Activate the version. You can do this by viewing the versions of the desired Data Table, and clicking Activate in the Actions dropdown for your desired version.The Data Table node only lists tables that have an active version. Tables created from BookIt > Data Table Management use the Single Graph business unit. For the full steps, including CSV header formatting, versions, and the Download, Replace, and Delete actions, see Routing - Data Table Based Routing Guide. Using an Existing Orchestration Table A Data Table that already routes records in Orchestration can also schedule meetings in BookIt. To get it ready: Open the table from Data Table Management and click Edit Columns.Add the BookIt output columns you need. Your existing Owner column can serve as the main host, so you don't need a separate main host column. To book meetings in BookIt for Forms, the table also needs a Forms Meeting Type column. Click Done Editing after adding your desired BookIt-specific columns. On the next page, fill in the new BookIt columns for every row. A new Forms Meeting Type column starts with every cell flagged as an error, and the table won't save until each cell has a meeting type or [NONE]. Blank Handoff Meeting Type cells fill in with Default Meeting Type.Check the pools in your Owner column. BookIt looks for a BookIt pool with the same name, so make sure one exists for each pool the table names, and reference pools by name. A pool referenced by ID points to that specific pool, so an Orchestration pool ID won't resolve to a BookIt pool. If BookIt has no matching pool, the prospect follows the Invalid Group edge.Check the users in your Owner and additional host columns. Each one must be authorized for BookIt and have access to the BookIt product, or the prospect follows the Insufficient User Access edge.Check your input columns. Each one needs a value BookIt can compare it with, as listed in Input Sources above. For example, a column that matches on a Lead field in Orchestration needs a matching form field, record field, or variable in your BookIt graph.Save the table and activate the version. Activating a version updates routing in every graph that uses the table, including your Orchestration graphs. Please Note: BookIt output columns count toward the table's 20-column limit. BookIt Output Columns BookIt reads the following output columns when the node is in Schedule a meeting mode. A table can have only one column of each of these types. The exception is Owner/Main Host: a table can have several Owner columns, and you choose which one the node uses as the main host. Column typeWhat it controlsAcceptsUsed byOwner/Main HostThe meeting's main hostOne user or one round robin pool, or [NONE]BookIt for Forms and BookIt HandoffRequired Additional HostsAdditional hosts who must be free for a time to be offeredOne or more usersBookIt for Forms and BookIt HandoffOptional Additional HostsAdditional hosts who are invited whether or not they're freeOne or more usersBookIt for Forms and BookIt HandoffForms Meeting TypeThe meeting type or types offered to the prospectOne or more BookIt for Forms meeting types, or [NONE]BookIt for FormsHandoff Meeting TypeThe meeting type for the suggestionOne BookIt Handoff meeting type, or Default Meeting TypeBookIt HandoffHandoff LocksWhat the scheduler can't changeAny combination of Main Host, Additional Hosts, and Meeting TypeBookIt Handoff Owner/Main Host Enter a specific user or a round robin pool. An Owner column in a Data Table is the main host when the table is used in BookIt.Enter [NONE] on rows that should match but not be scheduled. These rows follow the Do Not Schedule edge. See Routing Prospects Away from Booking below.An empty main host cell can be saved, but if a row with an empty main host matches in Schedule a meeting mode, the prospect follows the Invalid/Inactive User edge. Use [NONE] when you mean not to schedule.When you reference a pool by name, BookIt looks for a BookIt pool with that name when the prospect routes. If there isn't one, the prospect follows the Invalid Group edge. Required and Optional Additional Hosts Users in Required Additional Hosts must be available for a time slot to be offered. Users in Optional Additional Hosts are added to the invite, but their availability isn't checked, so the meeting can be booked even when they're busy. The main host is always required.To list more than one user in a cell, separate them with a semicolon (;).Additional hosts must be specific users. You can't save a table with a pool ID in either additional host column, and if a value resolves to a pool when the prospect routes, the prospect follows the Invalid/Inactive User edge.Leave the cell blank or enter [NONE] when the row has no additional hosts. Forms Meeting Type Select one or more BookIt for Forms meeting types. When a cell has more than one, the prospect picks from them on the Multiple Meeting Types page, in the order they appear in the cell. In the table, drag the meeting types to change the order.Every cell needs a value. The table won't save with a blank Forms Meeting Type cell. On do-not-schedule rows, enter [NONE].If a row has a main host but its Forms Meeting Type is [NONE], the prospect follows the Meeting Type Invalid edge. The node shows a warning in Meeting Parameters when this column contains [NONE] or empty cells.Only active BookIt for Forms meeting types can be selected. Personal meeting types aren't available.Meeting type names are case-sensitive, so "Demo" and "demo" are two different meeting types. Handoff Meeting Type Select one BookIt Handoff meeting type, or keep Default Meeting Type to book the default meeting type from your BookIt Handoff settings.Blank cells, including blank cells in an uploaded CSV file, fill in automatically with Default Meeting Type.To keep the scheduler from changing the meeting type, add Meeting Type to the row's Handoff Locks cell. Handoff Locks Choose any combination of Main Host, Additional Hosts, and Meeting Type.A locked host can't be removed from the meeting, but the scheduler can still add other hosts. A locked meeting type can't be changed.Additional Hosts locks all of the row's additional hosts together. Main Host and Meeting Type lock separately.Leave the cell blank to lock nothing. BookIt for Forms graphs ignore this column. Other Output Columns Any other output column, such as a Text, Number, or True/False column, is a regular output. Regular outputs can be stored in variables in either node mode. See Field Mappings below. Please Note: Owner/Main Host, additional host, meeting type, and Handoff Locks values are only used to book or suggest the meeting. They can't be stored in variables. Formatting BookIt Columns in a CSV File Reference users by their Salesforce User ID. 15-character IDs are converted to 18 characters.Reference meeting types by name, and pools by name or ID.Separate multiple values in one cell with a semicolon, for example Demo;Intro Call or Main Host;Meeting Type.Enter [NONE] in the Owner/Main Host and Forms Meeting Type columns on do-not-schedule rows.Keep each cell to 255 characters or fewer. The upload fails if any cell is longer. When you download a table, meeting types and pools are exported by name, so you can edit the file and upload it again. Adding the Data Table Node to a BookIt Graph In the LeanData app, open your BookIt for Forms or BookIt Handoff graph in FlowBuilder. We recommend making changes on a copy of the graph.From the node bar, drag a Data Table schedule node onto the canvas and connect it to your graph. On the canvas, the node shows as Schedule: Data Table.Click the node to open its settings. For more on building BookIt graphs, see BookIt Routing - BookIt FlowBuilder Guide. Configuring the Data Table Node Node Name and Description By default, the node is named Schedule Meeting with Data Table. Give it a name that describes what it routes, and use Description to note anything a teammate should know before changing it. Data Table Selection Select your Data Table from the picklist. Only tables with an active version are listed, and the node shows the name of the active version. The list includes every table with an active version, whatever its business unit. Click View Data Tables to open Data Table Management. What Should Happen When a Row Matches? Choose the node's mode: Schedule a meeting: Book with the host and meeting type from the matched row. In BookIt for Forms, the meeting is booked with the prospect. In BookIt Handoff, the matched host and meeting type are suggested to the scheduler, who completes the booking.Output to variables: Store the matched row's values as output variables for use later in the graph. No meeting is scheduled. The mode is saved with the graph. Once the graph is deployed, the node always runs in the mode you chose. Field Mappings Input fields read values from the prospect or record to find the matching row. Output fields store values from the matched row. Input Fields For each input column in the table, choose the value it is compared with: a form field (BookIt for Forms only), a field on the matched record, or a variable. Rows are checked from top to bottom, and the first match is used. Output Fields Output Fields are optional. Map any regular output column to a variable, then choose the Overwrite setting: If Blank: Writes the row's value only if the variable doesn't already have a value from earlier in the graph.Always: Always writes the row's value, replacing any earlier value. How you use these variables depends on the mode. In Schedule a meeting mode, use them in the node's Salesforce Event settings, or pass them to the next node on the Do Not Schedule edge. In Output to variables mode, use them anywhere later in the graph. Meeting Parameters The Meeting Parameters section only appears in Schedule a meeting mode. It lists each scheduling detail the matched row can supply: Owner / Main Host: Select the Owner column to use as the main host. You can't save the node in Schedule a meeting mode until this is set.Required Additional Hosts, Optional Additional Hosts, Forms Meeting Type (BookIt for Forms) or Handoff Meeting Type (BookIt Handoff), and Handoff Locks (BookIt Handoff): These are picked up from the table automatically. If the table has no column for one of them, its row in Meeting Parameters says so. The node has no separate host, meeting type, or lock fields of its own. All of these come from the matched row. Distribution Method The distribution method applies when the matched row's main host is a count-based round robin pool. You won't know which row a prospect matches until it routes, so set a distribution method even if only some rows use pools. Pooled Availability: Shows the combined availability of every pool member, so the prospect sees the most time slots. See BookIt for Forms: Pooled Availability.Round Robin Distribution: Offers times for the pool member with the fewest meetings, for the most even distribution. If that member doesn't have enough open times, BookIt adds members in order of meeting count until enough times show on the scheduling page.Manual Selection (BookIt Handoff only): Lets the scheduler choose the pool member. See the BookIt Handoff Admin Guide. Order-based pools always assign in pool order and ignore this setting. Respect User Schedules Turn on Respect User Schedules to avoid booking hosts during their configured vacations. When this is on, the Out of User Schedule edge appears under Advanced Settings. For more on vacations, see BookIt Vacation Handling. Event Creation The Data Table node has the same Salesforce Event settings as other BookIt schedule nodes: Create Salesforce Event, Related To, Assigned To, Event Subject, and additional event fields. For details on each setting, see BookIt - Schedule Meeting with Territory Node Guide. Variables from the node's Output Fields can fill in event fields, for example writing a row's segment to a custom Event field. Hosts from the table are not available as variables, so they can't be used with User from a Variable or as merge fields in the event. Advanced Settings Under Advanced Settings, each edge defaults to End of Flow. Point an edge at another node to handle that outcome. The edges available depend on the node's mode. Schedule a Meeting Mode Data Table Rows Not Met: The prospect didn't match any row in the table.Do Not Schedule: The prospect matched a row whose main host is [NONE]. Nothing is booked, and the row's output variables are passed to the next node.Meeting Type Invalid: The matched row's meeting type can't be used. This happens when a BookIt for Forms row has a main host but a [NONE] meeting type, or when the meeting type no longer exists.Invalid/Inactive User: The matched host isn't a valid, active Salesforce user, the row's main host cell is empty, or an additional host resolves to a pool.Insufficient User Access: The matched host isn't authorized for BookIt or doesn't have access to the BookIt product.Invalid Group: The matched pool doesn't exist as a BookIt pool.Out of User Schedule: Respect User Schedules is on and the host is unavailable because of a configured vacation.No Round Robin Members Available: No pool member is available to book.Variable Not Found: A variable mapped to an input column isn't valid when the prospect routes. When the meeting is booked successfully, the graph ends. Booking is always the last step in a BookIt graph, so this mode has no Next Node edge. Output to Variables Mode Next Node: The prospect matched a row and its output variables are set. The graph continues here.Data Table Rows Not Met: The prospect didn't match any row in the table.Variable Not Found: A variable mapped to an input column isn't valid when the prospect routes. Routing Prospects Away from Booking Some prospects match your criteria but shouldn't get a meeting, such as students, competitors, or existing customers. Rather than adding a decision node in front of the Data Table node, you can handle them in the table itself. In the Data Table, set Owner/Main Host to [NONE] on each row you want to turn away. In BookIt for Forms tables, also set Forms Meeting Type to [NONE] on those rows.Add a regular output column, such as a Text column named Redirect URL, and enter the page each row should send prospects to.In the Data Table node, use Schedule a meeting mode and map the Redirect URL column to a variable under Output Fields.Connect the Do Not Schedule edge to a Redirect to URL node that uses that variable. Prospects who match a [NONE] row skip booking and go to the page set on their row, so different segments can land on different pages. For setup of the redirect node, see BookIt for Forms - Redirect to URL Node. Example: OnPoint doesn't book demos with students. Connie adds a row near the top of her table that matches emails ending in .edu, sets the main host and meeting type to [NONE], and sets Redirect URL to OnPoint's education resources page. Student submissions follow the Do Not Schedule edge to a Redirect to URL node, while everyone else is booked with the host on their row. In Output to variables mode there is no Do Not Schedule edge. To turn prospects away in that mode, add a regular output column such as Disqualified (True/False), map it to a variable, and branch on it with a decision node after the Next Node edge. See BookIt True/False Decision Node Guide. Stamping Field Values with Output to Variables In a Routing Links graph, you can use a Data Table to decide which values to write to the Lead or Contact before the meeting is booked: Add a Data Table node in Output to variables mode and map the output columns you want to stamp, such as Segment or Region, to variables.Connect its Next Node edge to an Update Record or Create Record node that writes those variables to the record.Continue to the schedule node that books the meeting. The Data Table decides the values, and the record node writes them. Update Record and Create Record are Routing Links nodes, so this pattern applies to Routing Links graphs. For more, see BookIt Links & BookIt for Forms - Routing Links. You can also place two Data Table nodes in a row that use the same table: one in Output to variables mode to set variables, followed by one in Schedule a meeting mode to book the meeting. A single node can't do both, because booking is always the last step in a graph. Please Note: A meeting type stored in a variable can't set the meeting type in another schedule node. To book different meeting types for different rows, use a meeting type column with a Data Table node in Schedule a meeting mode, or route to separate schedule nodes with a decision node. Sharing a Data Table with Orchestration Orchestration and BookIt use the same matching logic, so a shared table matches the same way in both. A few things work differently on the output side: Input columns are shared. Map them separately in each graph's node, since the values come from a Lead or Contact in Orchestration and from a prospect or record in BookIt.Pools resolve by name within each product. When a cell names a pool, an Orchestration graph uses the Orchestration pool with that name and a BookIt graph uses the BookIt pool with that name. If BookIt has no pool with that name, the prospect follows the Invalid Group edge.Meeting types are product-specific. BookIt for Forms reads only the Forms Meeting Type column and BookIt Handoff reads only the Handoff Meeting Type column. A table used by both can have both columns.Users need BookIt access. A user who owns records in Orchestration also needs to be authorized for BookIt to host meetings. If not, the prospect follows the Insufficient User Access edge.Version changes apply everywhere. Activating a new version updates routing in every graph that uses the table, in both Orchestration and BookIt. Monitoring Audit Logs: The BookIt for Forms and BookIt Handoff audit logs show the Data Table node's outcome, including the row the prospect matched and the edge it followed. Each row's ID (for example, R00000) appears in the Row ID column of the table, so you can find the row that was used. See the Audit Logs Guide.Meeting Logs: For meetings booked through the Data Table node, the meeting details panel shows how the meeting was booked, including the pool and distribution method when a pool hosted. See LeanData Scheduling - Meeting Logs Guide. Considerations Row order matters. The first matching row wins, so place specific rows above broader ones.All inputs must match. A row matches only when every mapped input column matches. To match on either of two values, add a row for each.Table limits. A Data Table can have up to 20 columns, 50,000 rows, and 50 versions. BookIt output columns count toward the 20-column limit. Each cell holds up to 255 characters.One column per BookIt type. A table can have only one Required Additional Hosts, Optional Additional Hosts, Forms Meeting Type, Handoff Meeting Type, and Handoff Locks column.Order-based pools. Order-based pools can be used as the main host in BookIt for Forms graphs. BookIt Handoff doesn't support order-based pools.Columns in use. You can't delete a column while the table is used by a graph in Orchestration, BookIt for Forms, or BookIt Handoff.Meeting types in use. You can't delete a meeting type that a Data Table in use references. Remove it from the table first.Semicolons in meeting type names. Semicolons separate values in multi-value cells, so a meeting type whose name contains a semicolon can't be used in a Forms Meeting Type cell. FAQs Can I use the same Data Table in Orchestration and BookIt? Yes. Add the BookIt output columns you need to the table, and map the input columns in each graph's Data Table node. Your existing Owner column can be used as the main host. Which columns does a table need to book meetings? An Owner/Main Host column. Tables used in BookIt for Forms also need a Forms Meeting Type column. In BookIt Handoff, the Handoff Meeting Type column is optional. Without it, suggestions use the default meeting type from your BookIt Handoff settings. Can one Data Table node book a meeting and also pass values to later nodes? No. Booking is always the last step in a BookIt graph. Use a Data Table node in Output to variables mode first, then a second Data Table node in Schedule a meeting mode, both pointing at the same table. Why did a prospect follow the Invalid/Inactive User edge when the row has a host? Check that the main host is an active Salesforce user, that the main host cell isn't empty, and that neither additional host column contains a pool. Why did a prospect follow the Meeting Type Invalid edge? In BookIt for Forms, the matched row most likely has a main host but [NONE] as its Forms Meeting Type. Pick a meeting type for that row, or set the main host to [NONE] if the row shouldn't be scheduled. What is the difference between [NONE] and an empty main host cell? [NONE] means the row should match but not be scheduled, and the prospect follows the Do Not Schedule edge. An empty cell in Schedule a meeting mode is treated as a missing host, and the prospect follows the Invalid/Inactive User edge. Summary Data Table Based Routing in BookIt lets you route meetings from rows in a Data Table instead of chains of nodes. A matched row can set the main host, required and optional additional hosts, meeting types, and BookIt Handoff locks, or mark a prospect as one you don't want to schedule. Use the Data Table node in Schedule a meeting mode to book or suggest meetings, or in Output to variables mode to pass values to later nodes, and share the same tables with your Orchestration graphs. For questions or additional assistance, please contact LeanData Support.