Wheelhouse®
QuickBooks Online Integration
Custom Fields and Forms
System Administration
Troubleshooting Checklist
Document Auto Number Format
Sale Shipment Records and Tracking Information Emails
Peripherals and Equipment Requirements
Navigation and Definitions
Understanding Order Flow in Wheelhouse
Understanding People and Organizations in Wheelhouse
Admin List Views and Single Record Views
Document Categories
Logging In and Getting Started
Left Menu Navigation
Advanced Search Techniques
User Administration
User Management: Adding, Editing, and Revoking Access
User Profiles and Roles
Choosing a User Profile
Defining or Adjusting Teams
Understanding Wheelhouse Login Types
Reports, Import, Exports, and Document Templates
Running Reports
Creating Reports on Quotes, Sales, and Outside Reps
Exporting to Excel
Preparing Excel and Word Templates for Data Merge
Quality Mangement
Adding QCIR Templates
QC Non Conformance Reports (NCRs)
Adding Quality Control Inspection Records (QCIR) in Shop Work
Order Management
Creating customers, quotes and sales
Order Management Guide
Adding Dealer and Outside Rep Logins
Using Order Flags and the Flag First Configs Option
Closing a Sale
External Agent Access Levels
Printing and Emailing Quotes and Sales
Production Routing and Tracking
Shop Work and QR Scanning
Shop Work: Priority Flags and Fixed Position
Merge Line Items at a Certain Step (Stash & Merge Functionality)
Stopping Work Center or All Running Operations at the End of the Shift
Bin Locations
Shop Work
Viewing/Adding/Resolving Work Order Issues
Production Scheduling
Labor Routings
Production Definitions
External Connections - API
Items and Configurators
Product Configuration in Wheelhouse
Item Overrides: Name, Pricing, and Discounts
Public Item Selector AKA Public Display Categories
Deploying A Configurator to Another Environment
Item and BOM Import Action
Wheelhouse Change Log
Table of Contents
Dino Script® Language Reference
Appendix A: Trestle®/Dino Script® Integration
A: Table of Contents
A: Commands
A: Dynamic and DynamicProxy
A: Advanced Command Arguments
A: Introduction
A: Files
A: Direct Links - URLs and Downloads
A: Running SQL Queries
A: NPOI and Excel, DocX and Word
A: Embedded Apps with MS Access Files
A: Returning JSON Data
A: Host and Target
A: Command Arguments
A: Creating/Running a Command
Adding New Functionality with Dino Script XCommand™
Introduction
Dino Script™ Table of Contents
Operators
Concepts
Syntax
Expression Types
Keywords
Variables
Blocks and Scopes
Built-In Functions
Custom Functions (defs)
Anonymous Functions
Conditional Statements
The Context Object
FAQ
Dino Cookbook
Sandbox In-Depth
Functions as Delegates
Style Guidelines
Native Types
Aliasing
Other Dino Scripts
- All Categories
- Wheelhouse®
- Reports, Import, Exports, and Document Templates
- Preparing Excel and Word Templates for Data Merge
Preparing Excel and Word Templates for Data Merge
Updated by Dale Mandeville
Wheelhouse is capable of merging data into template documents created with Microsoft Excel and Microsoft Word. Once the merge is complete, the file may be exported to a PDF or left as the original file type. File merge capability is useful for many things - from creating a custom format for a sales order to creating an nicely formatted report, a customer letter, or a work order template. Using scripting, the resultant report may be stored in the system, emailed as a PDF, or sent to another system.
Creating a Template
- Setup the File... if output is paper, set page width
- setup columns - cannot use merged cells if text needs to be wrapped or AutoFit Row Height
- Create layout
- Sometimes it is helpful to manually enter test data to make sure wrapping and auto-fit are working correctly in the template document.
- Verify that document prints correctly.
- Switch test data to template field data. If you're already using a similar template, see that template for the available fields. Template fields are customized per company. Contact your developer for a list of available fields. Template fields follow the format
${field_name}
. - Save the document to the Template Documents list.
- Add keywords based on the terms that your developer uses for identifying the correct templates. Again, looking at the exiting template documents will reveal the keywords that are in use.
- If you don't already have the merge function available, ask your developer to create an action to connect the template to the data.
Troubleshooting
- In Excel, if Autofit height not working properly:
- Verify that Autofit is switched on for the cell.
- Verify that text wrapping is enabled for the cell.
- Verify that the autofit cells are either (1) single row or (2) not merged cells
- Try exporting to Excel instead of PDF to verify that the data is getting properly inserted.
- If there are missing fields or fields where data is not filling correctly:
- Verify that the field_name is available in the action be used. (Check with your developer.)
- Verify that you aren't missing any qualifiers such as the ${ }
- If cells in Microsoft Word tables are getting split across pages, you can change these settings:
- Table Properties: Uncheck "Allow row to break across pages"
- Paragraph Properties: Check "Keep lines together"
- If certain paragraphs need to be kept together, try the Paragraph: Keep with Next setting.