Processing & Scheduling

Generate documentation or export metadata via the UI or the CLI — with scheduling, output options, and full CLI command reference.

UICLIRapid BI CatalogTableau ServerLocal FilesScheduling

Rapid BI Catalog allows you to generate documentation or export Tableau metadata through both a web interface and a command-line interface (CLI). Choose the method that fits your workflow and environment.

Licence Required
Manual processing (local files and BI Server sources) is available on all plans. Automated / scheduled documentation requires the Professional or Enterprise plan. See License Management.
Usage limits
Your plan sets limits on how many files you can process — overall and per period (monthly or yearly), with separate manual and scheduled allowances and a cap on unique Tableau Server workbooks. See License Management for your plan's limits.

Using the UI

Step 1: Choose a Workbook Source

Processing source tabs
Three source options: Rapid BI Catalog server files, Tableau Server, and Local Files.

a. Rapid BI Catalog (Server Files)

Process workbooks stored on the server where Rapid BI Catalog is installed.

  1. Select the Rapid BI Catalog tab.
  2. Click Select a file or a folder.
  3. Choose your output type (File or Database).
  4. Optionally enable Schedule for later.
  5. Click Execute now.

b. Tableau Server / Tableau Cloud

Process workbooks directly from your connected Tableau Server or Cloud environment.

  1. Select the BI Server tab.
  2. Choose an Environment, Site, and one or more Projects.
  3. Choose workbook selection:
    • All Workbooks — process every file in the selected projects
    • Select Workbook(s) — choose specific files
  1. Choose output type, then run or schedule.
How Tableau access works
Interactive browsing and processing use your own Tableau Connected App identity, so you only see the sites, projects, and workbooks you can access in Tableau. On sites that use Direct Trust, your account must first be picked up by User Discovery — otherwise processing is blocked with an "identity not discovered" message, and you should ask your administrator to run discovery. On sites that use OAuth 2.0 Trust, please allow pop-ups for Rapid BI Catalog so the one-time Tableau sign-in can complete.

c. Local Files (Upload)

Upload Tableau workbooks from your local machine for ad-hoc processing.

  1. Select the Local Files tab.
  2. Click Choose Files to upload .twb or .twbx files.
  3. Choose output type.
  4. Click Execute now.
Note — Local Files and Scheduling
Scheduling is not available for the Local Files option. Since files are uploaded from your local machine at the time of processing, there is no persistent server-side file path to schedule against.

Step 2: Choose Output Type

File(s)

Generates documentation files in one or more formats:

FormatBest for
HTMLWeb-friendly, browseable output
PDFPrintable, shareable documentation
DOCXEditable Word documents
ExcelTabular review and comparison
CSVMachine-readable metadata per section

Database(s)

Exports metadata to a configured database for querying, governance dashboards, or analytics:

  • MySQL
  • MS SQL Server
  • PostgreSQL
Note — Database Output Performance
Processing files with the database output option always uses a single thread.

Keep Latest Option

When reprocessing workbooks that have already been processed before, you can control how existing records are handled with the Keep Latest toggle:

Keep LatestBehaviour
On (selected)Previous output records for the file are deleted, and only the new records are retained. Keeps the dataset clean and current.
Off (not selected)Previous records are marked as outdated (latest = 0 on MySQL/MS SQL, latest = false on PostgreSQL) while the new records are written with latest = 1 / latest = true respectively. Allows historical comparison.

Real-Time Logs

A logs terminal at the bottom of the page automatically expands when processing starts. It shows real-time progress including which workbooks are being processed, extraction stages, and any errors.

Viewing Historical Runs
Full execution history is available on the Logs page.

Step 3: Schedule for Later (Optional)

Enable the Schedule for later toggle and configure:

FieldDescription
Job TitleA descriptive name for the job
Schedule TimingDate and time for the first run
Schedule FrequencyHow often the job repeats (see table below)
OptionDescription
One TimeRuns once at the specified time, then stops
Every DayRuns daily at the specified time
Every WeekdayRuns Monday through Friday at the specified time
Every [Day of Week]Runs weekly on that specific day (e.g., Every Monday)
Time Zone
Scheduled jobs execute based on the time zone configured by the Admin in Settings.

How Scheduled Jobs Authenticate

Scheduled jobs run unattended, so they cannot use your personal sign-in. Tableau Server and Tableau Cloud jobs instead authenticate with the site's Service Account — a dedicated Tableau token — so a Service Account must be configured for a site before you can schedule Tableau jobs against it. Jobs that process files already stored on the Rapid BI Catalog server do not need one.

Using the CLI

The bicatalog command-line interface processes Tableau files available on the server's file system — workbooks you have downloaded or placed in a folder there. Process Tableau Server and Tableau Cloud content from the web UI, which manages Connected App authentication for you; direct command-line processing of Tableau Server / Cloud sources is not available currently.

Generate Documentation

The following must be available for the CLI command:

  1. The source file storage directory
  2. The desired output format
  3. The destination folder for output files

Command

Terminal
bicatalog start -s <sourcefolder> -f <outputformat> -o <outputfolder>
ParameterDescription
-sPath to source folder containing Tableau files (.twb / .twbx)
-fOutput format: pdf | html | excel | csv | docx | all
-oOutput folder path where generated files are written

Example

Terminal
bicatalog start -s /home/source -f pdf -o /home/output

Export Metadata to Database

Prerequisite
You must configure a database connection in Rapid BI Catalog before running this command. See Database configuration.

Command

Terminal
bicatalog start -s <sourcefolder> -f db -k <keeplatest> -o <outputfolder>
ParameterDescription
-sSource folder containing Tableau files
-fUse db for database export
-ktrue — delete previous records and keep only the latest. false — mark previous records as outdated (latest = false) and add new records with latest = true

Example

Terminal
bicatalog start -s /home/source -f db -k true

Output Folder Naming

If two Tableau workbooks have the same name but different file extensions (e.g., Superstore.twb and Superstore.twbx), the output folder names are automatically qualified to avoid conflicts:

ScenarioOutput folder name
Single extension onlySuperstore-05022025-113105
Both .twb and .twbx presentSuperstore-TWB-05022025-113105 and Superstore-TWBX-05022025-113105

Next Steps