Dynamics SL – Page 4 – Spitfire Client Services

KBA-01216: Customer and Vendor documents names do not match Microsoft Dynamics SLKBA-01216: Customer and Vendor documents names do not match Microsoft Dynamics SL

January 5, 2011| Dorothy McGovern|

Question: Why doesn‘t my Customer (Vendor) document in Spitfire match the name of the Microsoft Dynamics SL customer (vendor)? Answer: If the option is disabled in ICTool on the Dynamics

KBA-01202: Automatic creation of Spitfire AP Voucher DocumentsKBA-01202: Automatic creation of Spitfire AP Voucher Documents

January 5, 2011| Dorothy McGovern|

Question: When does Spitfire create a voucher document for a Microsoft Dynamics SL AP Voucher? Answer: Spitfire creates AP vouchers in one of two ways, both of which require the

KBA-01275: Recording Owner Direct CommitmentsKBA-01275: Recording Owner Direct Commitments

September 13, 2010| Dorothy McGovern|

Question: How can I include a Commitment on my project that should not export to Microsoft Dynamics SL? Answer: Create your Commitment. Check the Owner Direct check box on the

KBA-01098: Are Spitfire Submittals included in Microsoft Dynamics SL Subcontract Payment Analysis?KBA-01098: Are Spitfire Submittals included in Microsoft Dynamics SL Subcontract Payment Analysis?

April 7, 2009| Dorothy McGovern|

Question: When a Submittal is entered in Spitfire, will Microsoft Dynamics SL Subcontract Payment Analysis include it? Answer: No. Submittals are not included in Payment Analysis. KBA-01098; ;

KBA-01066: How does the Spitfire dashboard find the shared Microsoft Dynamics SL files?KBA-01066: How does the Spitfire dashboard find the shared Microsoft Dynamics SL files?

February 10, 2009| Dorothy McGovern|

Question: How does the Spitfire dashboard find the shared Microsoft Dynamics SL (DSL) files? Answer: The most prevalent and successful way for sfPMS to locate the shared DSL files on

KBA-01356: Restoring a Spitfire database over another Spitfire database (when integrated with Microsoft Dynamics SL)KBA-01356: Restoring a Spitfire database over another Spitfire database (when integrated with Microsoft Dynamics SL)

October 6, 2008| Dorothy McGovern|

Purpose & Scope: How to refresh a Test Spitfire database from a Live Spitfire database when integrated with Microsoft Dynamics SL Procedure: If necessary, follow the instruction in KBA-01203, Restoring a Microsoft Dynamics

KBA-01360: Automatically Assigning Microsoft Dynamics SL WKCC codes to Costs CodesKBA-01360: Automatically Assigning Microsoft Dynamics SL WKCC codes to Costs Codes

September 15, 2008| Dorothy McGovern|

Question: In Microsoft Dynamics SL, I need to assign specific Workers Comp codes to specific Cost Codes whenever that Cost Code is added to a project. Can Spitfire automatically do

KBA-01280: Moving the Spitfire Database to another SQL ServerKBA-01280: Moving the Spitfire Database to another SQL Server

March 17, 2008| Dorothy McGovern|

Purpose & Scope: You can move the backend data for a Spitfire site from one SQL Server to another. The Spitfire database is not a stand-alone database. It is linked with either your Microsoft

KBA-01259: Document Types that require Microsoft Dynamics SLKBA-01259: Document Types that require Microsoft Dynamics SL

March 22, 2007| Dorothy McGovern|

Question: Which Spitfire document types are strictly integrated with Microsoft Dynamics SL? Which Spitfire document types should I disable on a site without integration to Microsoft Dynamics SL? Answer: The following Spitfire

KBA-01113: PCO Request Print requires Contract ValueKBA-01113: PCO Request Print requires Contract Value

November 21, 2006| Dorothy McGovern|

Question: Why is the summary section at the bottom of the PCO Request blank? Answer: The summary section of the PCO Request normally contains information similar to the lines below.

Tag: Dynamics SL