Skip to contentSkip to content
Spitfire Client Services

Spitfire Client Services

  • Support
    • KBA
    • Downloads
      • Implementation – Getting Started
      • Implementation – Templates
    • Training
  • Documentation
    • Focus Guides/TWP
    • What’s New in Spitfire
    • System Requirements
  • Newsletter Articles
  • Webinars
  • Video Library

KBA-01027: Why is the Account Category lookup on my Project Change Orders blank?

Spitfire Client Services >> Knowledge Base>> KBA-01027: Why is the Account Category lookup on my Project Change Orders blank?
September 21, 2011September 21, 2011| Dorothy McGovernDorothy McGovern|
Categories:
  • Knowledge Base

Question:

When I create a Change Order document, the lookup for my Account Categories is blank. Why?

Answer:

sfPMS includes only those Account Categories that have been designated for Change Orders in the Account Category Lookup in Microsoft Dynamics SL (if you are integrated) or the Account Categories tool (if you are not integrated).

To indicate that an Account Category is used on Change Orders on Integrated Sites:

  1. In Microsoft Dynamics SL, open Account Category Maintenance in the Project Controller module.
  2. In the Change Orders field, select Yes.
  3. Save your changes.

If the Change Orders field is not visible (in the Account Category Switches section), contact your Microsoft Dynamics SL System Administrator. The Change Orders field is a Spitfire customization to the Account Category Maintenance (PA.ACC.00) screen.

To add Account Categories on non-Integrated Sites:

  1. Go to the Account Categories tool on the System Admin Dashboard.
  2. Add rows for each Account Category you want used in the system.
  3. Accept each row and save.

Additional Comments:

All of Spitfire‘s Microsoft Dynamics SL customizations are distributed as Supplemental Product VBA customizations.


KBA-01027; Last updated: November 10, 2016 at 9:02 am;

Tags: Account Category, Change Order Process

Post navigation

PREVIOUS Previous post: KBA-01025: How do I create a job category for Spitfire in SQL Agent job management?
NEXT Next post: KBA-01028: Why do my clients get the message that Spitfire Extensions are not available?

Related Post

KBA-01128: Logging into Microsoft Dynamics SL from SpitfireKBA-01128: Logging into Microsoft Dynamics SL from Spitfire

Question: When I access Microsoft Dynamics SL (DSL) from Spitfire, I‘m asked to login to DSL even though I‘m already logged into DSL. Why? When I open a Microsoft Dynamics

Read MoreRead More

KBA-01037: Full-text Catalog has been lostKBA-01037: Full-text Catalog has been lost

Problem: A ‘Full-text catalog File Catalog (or sfDocCatalog) has been lost‘ message is displayed in my Log file. What do I do? Solution: The catalog may have been lost because of a

Read MoreRead More

KBA-01302: ProjectConfig: Advanced GL Subaccount MappingKBA-01302: ProjectConfig: Advanced GL Subaccount Mapping

Question: Can I set up a GL Subaccount mapping to use when creating a project based on anything other than sub type or contract type? Answer: Yes.  The ProjectConfig rule

Read MoreRead More
  • KBA-01876: Using Workflow to Approve Docs Regardless of User Permission
  • KBA-01878: Releasing Retention on an SOV Pay Application
  • KBA-01877: Assembled PDF Output in Power UX
  • KBA-01874: Bulk Export from Catalog in Power UX
  • KBA-01875: Viewing Field History in Power UX
  • Client Webinars
  • Documentation
  • Knowledge Base
  • Newsletter Articles
  • Rules
  • Spitfire Reports
  • Training
  • Uncategorized
  • Videos (Power UX)
  • Videos (Quick, Basic Q&A)
  • What's New
  • Workflow Scripting

Meta

  • Log in

Spitfire Management, LLC
5219 Monticello Avenue #5444
Williamsburg, VA 23188

VW Machine Learning WordPress Theme Copyright 2025 Spitfire Management, LLC. All rights reserved.

Scroll Up