Custom Excel Exports with DISCUS - version 1.32 - export to user-defined templates

Sep 11, 2026

Uploaded by Mali

Explains how DISCUS enables exporting characteristic data into user-defined custom Excel templates, supporting multiple customer needs and varying formats through a single methodology. Covers creating templates with token placeholders, mapping tokens to data entered in DISCUS, and importing into Excel sheets with optional tabs. Includes key export reminders (template reuse, case-sensitive tokens, token placement, handling empty values) and introduces common AS9102 Form 1 tokens with examples and output usage.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages15

Reading Time5 min

AccessFree to download

About Custom Excel Formats

Creating Custom Templates

4 Things to Remember Regarding DISCUS Exports to Custom Excel Formats

Form 1 of AS9102

Common tokens for AS9102 Form 1

Example: Exporting Form 1 data to an Excel template

Custom Excel Exports with DISCUS vers. 1.32 About Custom Excel Formats The Excel export capability is in the hands of the user! DISCUS now allows the export of characteristic data into user-defined custom Excel templates. Not only does this capability support the set up of AS9102 inspection forms, but can be used for more general inspection sheets as well. Multiple customers and varying formats can easily be satisfied using a single methodology with DISCUS. In order to perform the custom export to Excel a template will need to be created. The template will contain tokens which are like variables that will inform DISCUS of what type of data is to be exported as well as where and how it is to be imported into the Excel spreadsheet. Multiple sheets (tabs) can exist within a template file. The following picture illustrates what an Excel template with tokens might look like. Creating Custom Templates Creating a template requires properly formatting the tokens that you want to include in the export into the appropriate cells within the appropriate sheet(s) of your Excel file. There are many different tokens available and they can be strung together in various combinations as well as mixed among general text within the cells of the spreadsheet. The following will explain what some of the tokens represent as well as provide examples of some of the ways that they can be used. Each example will consist of a screen capture of the template file followed by a screen capture of the output from DISCUS. The tokens will be introduced according to the various forms that they relate to per AS9102 (i.e. Form 1, Form 2 and Form 3) but they can be Custom Excel Exports with DISCUS version 1.32 1 used to export data from DISCUS into a variety of Excel formats such as general inspection sheets. In addition to this it is possible to export data in raw tabular format for use in populating the tables of a database (i.e. Microsoft Access) or even to interact with Excel macros. Feel free to be creative and invent new ways of stringing together tokens to output data from DISCUS into your own custom formats! 4 Things to Remember Regarding DISCUS Exports to Custom Excel Formats: 1. Save any templates you create. They are reusable with DISCUS. 2. Tokens are case sensitive and must be typed as they are shown using the dollar sign ($), curly brackets ({ }) and the underscore sign (_ ) . 3. Data must be entered inside DISCUS and a properly formatted token representing the data must exist in a cell within the Excel template to successfully export that data. 4. General text can be used with tokens and combinations of tokens can be strung together. When tokens are applied only nonempty values from DISCUS will appear. Tokens with empty values (no data) will be ignored and skipped over during the import process. Form 1 of AS9102 The following table shows some of the common tokens that can be applied to Form 1 of a First Article Inspection sheet during an export from DISCUS to Excel. These tokens are general however and can be applied to any sheet of an Excel file (i.e . a general inspection format, not necessarily specific to Aerospace Standard AS9102) . Each of these types of data is optional and some may already exist in your template (i.e. your company name as well as the customer name may already be present in your template file and would not need to be exported out of DISCUS) . | Token Name | What it Represents… | Example(s) | | --- | --- | --- | | ${tdpComponentNumber} | The part number entered in the Part Number field of the Basics tab in the TDP Properties dialog box | 3110526191 | | ${tdpPartName} | The part name entered in the Part Name field of the Basics tab in the TDP Properties dialog box | Bracket | | ${tdpPartVersion} | The part revision level entered in the Part Revision field of the Basics tab in the TDP Properties dialog box | A | | ${tdpDrawingNumber} | The drawing number entered in the Drawing Number field of the Ba

FAQs

What is required to perform a custom export to Excel in DISCUS?

Create an Excel template containing tokens that indicate what data to export and where/how to import it. The tokens must be correctly placed in the appropriate cells and mapped to data entered in DISCUS.

Why do tokens need to be typed exactly as shown?

Tokens are case sensitive and must include the correct syntax, including the dollar sign ($), curly braces ({ }), and the underscore sign (_). Incorrect typing prevents successful export.

How does DISCUS handle empty token values during Excel import?

When tokens are applied, only nonempty values from DISCUS appear in the exported output. Tokens with empty values are ignored and skipped during the import process.

Sep 11, 2026

Uploaded by Mali