Versions Compared

Old Version 62

changes.mady.by.user Min Zeng

Saved on

compared with

New Version 63

changes.mady.by.user Min Zeng

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Account SettingDescriptionShortcodesExampleExample Shortcode
BC Tenant NameName of the Business Central Tenant to connect to.  Ask the development team for details please.

NULL
BC Environment NameThe name of a Business Central Sandbox environment.  Leave it blank if integrating with the real Business Central instance. 


BC API Version NumberThe API version number used in the transaction synchronization.  Ask the development team for details please. 


BC Cost Center Mapped Dimension NamesWhen mapping to dimensions, this allows the user to specify, positionally, the name of each dimension.  Enter the names of the configured dimensions, separated by the designated delimiter, in the same order the dimension values are specified in cost center mappings.  Matching dimension names and value lists need to exist in Business Central for the synchronization to succeed. 

NULL
BC Dimension DelimiterThe delimiter used to decode the cost center dimension string, A/P, A/R and G/L line dimention string 
|
Set Mapped Dimesnions at A/P Invoice LevelIf set to true, A/P transaction's GL line's cost center dimension will be set at the A/P invoice level.  other wise, A/P line's cost center dimension is set at the line level only. 


Set Mapped Dimensions at A/R Invoice LevelIf set to true, A/R transaction's GL line's cost center dimension will be set at the A/R invoice level.  other wise, A/R line's cost center dimension is set at the line level only. 


BC Tax CodeProjector will use this as the tax code in all transactions sent over to Business Central. Tax should be set up with a 0% rate, as Projector handles taxes as separate items.

PPSATAX
BC A/P Transaction Description Field FormatDescription field format for payment vouchers..
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AP" - Hardcoded to this string
  • {2} - AP Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Payment Voucher #
  • {7} - Vendor Invoice # on a payment voucher
  • {8} - Expense Document #

Projector {1} Txn#{2:D10},{0},{6}   ;{3};Exp Doc #{8};Vendor Ref #{7}
BC A/P Invoice Line Dimension MappingsAdditional A/P invoice line dimension delimited using BC Dimension Delimiter. Matching dimension names and value lists need to exist in Business Central for the synchronization to succeed. See above 
PVNo={6}|VendNo={7}
BC A/R Transaction Description Field Format (client level invoices)Description field format for client level invoices. The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name

Projector {1} Txn#{2:D10},{0},{6}    ;{3};{10} ({9})
BC A/R Transaction Description Field Format (PO level invoices)Description field format for purchase order level invoices. The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name

Projector {1} Txn#{2:D10},{0},{6}    ;{3};{13}
BC A/R Transaction Description Field Format (engagement level invoices)Description field format for engagement level invoices. The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name

Projector {1} Txn#{2:D10},{0},{6}    ;{3};{12} ({11})
BC A/R Transaction Description Field Format (project level invoices)Description field format for project level invoices.  The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable
  • {1} - "AR" - Hardcoded to this string
  • {2} - AR Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - Invoice #
  • {7} - Invoice Name
  • {8} = Client Number
  • {9} = Client Name
  • {10} = Purchase Order Number
  • {11} = Engagement Code
  • {12} = Engagement Name
  • {13} = Project Code
  • {14} = Project Name

Projector {1} Txn#{2:D10},{0},{6}    ;{3};{12} ({11})
BC G/L Journal IdentifierIf specified, lines will be added to an existing journal in Business Central, identified by this value. Otherwise, a new journal is created and lines added to the new entry.  If a matching journal could not be find in Business Central, GL transactions will fail. 

GL-10001
BC A/R Invoice Line Dimension MappingsAdditional A/R invoice line dimension delimited using BC Dimension Delimiter. Matching dimension names and value lists need to exist in Business Central for the synchronization to succeed. See code for BC A/R Transaction Description Field Format (project level invoices)
InvNo={6}|ClinNo={8}
BC G/L Code Field FormatThis field defines the journal code when Projector is creating journals. It supports two placeholders: {0} – Transaction Batch Number and {1} – GL Transaction Number. Default value is ‘{1}’.
  • {0} – Transaction Batch Number
  • {1} – GL Transaction Number


BC G/L Comment Field FormatComment field format for journal entries. 
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "GL" - Hardcoded to this string
  • {2} - GL Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - GL Batch #
  • {7} - The description on a transmitted cost card or the description on a reconciliation item
  • {8} - The expense report number on a transmitted cost card (not populated for reconciliation items)
  • {9} - Client Number
  • {10} - Client Name
  • {11} - Engagement Code
  • {12} - Engagement Name
  • {13} - Resource Display Name
  • {14} - Project Code
  • {15} - Project Name
  • {16} - Payment Voucher # (only populated when you have reconciliation items)

PPSAGJE
BC G/L Display Name Field FormatDisplay name field format for journal entries. 
  • {0} = Company Number
  • {1} - Accounting Period - Recommend you use period strings like 2022-02 for Feb, 2022 as it is fixed width and easily sortable

C{0}-AP{1}
BC G/L Transaction Description Field FormatDescription field format for journal entries. The limit is 100 char. 
  • {0} - Accounting Period - Recommend you use period strings like 2014-02 for Feb, 2014 as it is fixed width and easily sortable
  • {1} - "GL" - Hardcoded to this string
  • {2} - GL Transaction # - recommended you string format this to a fixed number of digits.
  • {3} - Your installation's account name
  • {4} - The display name of the user who sent the transaction
  • {5} - Date and time the transaction was sent from Projector
  • {6} - GL Batch #
  • {7} - The description on a transmitted cost card or the description on a reconciliation item
  • {8} - The expense report number on a transmitted cost card (not populated for reconciliation items)
  • {9} - Client Number
  • {10} - Client Name
  • {11} - Engagement Code
  • {12} - Engagement Name
  • {13} - Resource Display Name
  • {14} - Project Code
  • {15} - Project Name
  • {16} - Payment Voucher # (only populated when you have reconciliation items)

Projector {1} Txn#{2:D10},{0},{6}  ;{3};{14};{7};{8};{16};{13}
BC G/L Transaction Document Number Field FormatDocument Number field format for journal entries. 
DOC{1}
BC G/L Journal Line Dimension MappingsAdditional G/L invoice line dimension delimited using BC Dimension Delimiter. Matching dimension names and value lists need to exist in Business Central for the synchronization to succeed. 


Create Vendors in BC AutomaticallyTurn this setting on to have Projector create vendors in Business Central automatically as necessary.When Projector tries to send over an AP transaction and the vendor does not already exist in Business Central, Projector will attempt to create the vendor in BC. Note there is no ongoing synching of vendors, only initial creation.
0
Create Customers in BC AutomaticallyTurn this setting on to have Projector create customers in Business Central automatically as necessary.When Projector tries to send over an AR transaction and the customer does not already exist in Business Central, Projector will attempt to create the customer in BC. Note there is no ongoing synching of customers, only initial creation.
0

...