KBA-01371: Single Instance Doc TypesKBA-01371: Single Instance Doc Types

Question: Why can‘t I create a second Budget document before I approve the current one? Answer: Since budget revisions, forecasts and period distributions depend on the prior state when the

KBA-01374: Using the @DV function in Doc Template Computed FieldsKBA-01374: Using the @DV function in Doc Template Computed Fields

Summary: Spitfire‘s templates created in Microsoft Word offer the ability to dynamically compute new values based on existing data in the document.  The WordTemplateConfig rules (KBA-01323) and Nested Bookmarks (KBA-01348) can

KBA-01381: Where does the information on the Contract For field on the Project Summary come from?KBA-01381: Where does the information on the Contract For field on the Project Summary come from?

Question: I notice a Contract For field that is automatically populated on the Project Summary form of the SOV workbook.  Where does it get its information from? Answer: You can

KBA-01385: Print Preview in Microsoft Word Doc Templates can cause a save errorKBA-01385: Print Preview in Microsoft Word Doc Templates can cause a save error

Question: I opened a Word file created from a template, looked at it through Print Preview, then closed the file.  I clicked Yes at the ‘save changes?‘ dialog box, but

KBA-01387: Getting the most out of Bid Packages and the Competitive Bid WorkflowKBA-01387: Getting the most out of Bid Packages and the Competitive Bid Workflow

Summary: The Bid Package document can be considered a ‘wrapper‘ used to create a set of RFQ documents. Each RFQ should contain exactly the same information, but with a different vendor on

KBA-01402: What is the source for the values in the Project WIP report?KBA-01402: What is the source for the values in the Project WIP report?

Question: Where do the values in the Project WIP report come from? Answer: The values are a combination of amounts gathered from the Microsoft Dynamics SL (a.k.a. Solomon) tables, the

KBA-01413: Workflow Script Error: SET references invalid fieldKBA-01413: Workflow Script Error: SET references invalid field

Question: What causes the error: SET references invalid field? What causes the error Expression references invalid table name Answer: These errors are caused by a syntax error in the script, most

KBA-01414: Source Contact on Customer and Vendor documentsKBA-01414: Source Contact on Customer and Vendor documents

Question: Can I change the Source Contact on my Customer and Vendor documents? Answer: No, the Source Contact on these Doc types must be the primary company contact.  For this

KBA-01415: Changing the default Incl for file typesKBA-01415: Changing the default Incl for file types

Question: When I attach files to a Spitfire document, I notice that some files say Native on the Incl column, but I want them to be Assembled, so I have to change

KBA-01421: How to Configure Routes for Documents on Projects vs. Documents not on ProjectsKBA-01421: How to Configure Routes for Documents on Projects vs. Documents not on Projects

Problem: Can automated (predefined) Routes be created for documents based on whether or not the document has a ProjectID? Solution: Yes.  When creating an predefined Route (through the Routes tool