NAV/BC - How to email statements to multiple customers with different emails

• Complete SMTP setup
• On customer card>General>Document Sending Profile
• Setup and select a profile configured to email
• Email = Yes (Prompt for settings)
• Attachment = PDF
• File = PDF 
• Navigate>Customer>Document Layouts MUST be configured with specific emails per document, per customer
• Note, the email address of the customer and contact ARE NOT USED
• Default statement report is R1316
• C8800 Custom Layout Reporting
• Click on Report>Statement
• Enter starting and ending date
• Report Output = Email
• Tick print although email is missing
• A zip file is generated with all statements if it cannot email

Error "You cannot send the email, would you like to download the attachment"

• Ensure you use R1316
• Run the "Setup Email" wizard, then NEVER TOUCH the SMTP Setup screen again
• 
  

NAV / BC AL Extension fields missing after publish

 Add Applicationarea = All to all fields

NAV AL - Flowfield example

 tableextension 50017 "Item Journal Line Ext" extends "Item Journal Line"

{

    fields

    {

        field(50000; StdCost; Decimal)

        {

            FieldClass = FlowField;

            CalcFormula = Lookup(Item."Standard Cost" WHERE ("No."=FIELD("Item No.")));

           

        }

    }

}

Peachtree - How to connect to ODBC

• Create External user and password 
• Login as admin
• User>Setup user security
• Data Access/Crystal Reports
• Access from outside Sage 50
• With the following login info
• Set a password
• Username is always Peachtree
• Create odbc - use external user and password

BC/NAV - Assembly - How to pick specific lots for assemblies

  Turn off Create Movements Automatically field in the Assembly Setup to require manual movements for assembly picks.

Business Central on SQL Azure - The Federation Service endpoint login failed because the following audience URI does not match an AppIdUri or wtrealm in server or application configuration.

 Restart IIS

SSIS - Create Dynamic Data Connections for NAV/BC

https://www.sqlservercentral.com/articles/creating-a-robust-ssis-development-environment-using-the-ssis-catalog

• Right click data connection>Parameterize
• On the top, select "ConnectionString"
• The value field will show the entire connection string
• Put the entire thing into a parameter
• Switch the ConnectionString property to use a parameter
• Now you can update your parameter value with the exact connection string you want the connection to use.
• On each data connection, you can also go to Properties>Expressions
• Here you can use a variable as a connectionstring