Creating a pro forma invoice on dynamics 365 for finance and operations is a pretty straightforward task. A pro forma invoice is a crucial financial document that people use in businesses. In a nutshell, a pro forma invoice is more or less like an estimate that companies share with their client before sending them the actual invoice. The actual amounts can change if there is a difference in the quantity of material as well as the labor before preparing the final bill. Many people struggle to locate, view, or to print this document on dynamics 365 as it can be confusing. In this article I am going to demonstrate how to view/print  pro-forma invoice. A pro forma invoice is an invoice that is prepared as an estimate of the actual invoice amounts before the invoice is posted. You can print a pro forma invoice either for a customer invoice for a sales order or for a free text invoice. Step 1: Configure Print management from  Account receivable>Setup>Forms   Step 2: Right click on Customer invoice and click New Step 3: Go to All sales orders, Select an order which is in Open state.     Step 4: Go to Invoice tab and click on Pro forma Invoice     Step 5: In Quantity select All and in Print options enable Print Invoice     Step 6: You may click on Export to save the document or print it   Hope this helps!

In this blog article, we will see how we can create a project and deploy a dynamic 365 operations environment using Lifecycle services. Prerequisites: Azure Subscription Lifecycle Service Account Step by Step approach: Environment Setup  Azure Subscription: Login to the Azure portal using credential use below URL and buy Pay-As-You-Go subscription as LCS will consume more resource and if we choose start free option it will give error later when we deploy the VM. “https://portal.azure.com/” Once we done with the subscription go to the subscription tab and select the Access Control option and create a role select the role as the Contributor and Add a user select the user as the “Dynamic Deployment Services.” We can now login to the Lifecycle Services remember we should login in LCS using the account which has the admin access to the subscription. After login we can see the following screen. The first step in LCS is to create new project so click on (+) sign to create new project.  Once we click on (+) sign we’ll have different option the option may vary as per the version of LCS you are using, here we are setting up environment for development and learning purpose select the “Migrate, Create Solutions, and Learn” option. Enter the project details and click on the create option. All the information is related to the how you want your project settings to show and the methodology option let you select what you want to shows up on the default project information that shows up in lifecycle services so the migrate and create dynamic 365 for operation solution give you these options.  Once we click on create we’ll land to the life cycle project homepage Access the Azure subscription:- Scroll to the right and click on the project settings We are accessing the azure subscription so click on the Azure connectors options we’ll see the following screen. The first step is to authorize your organisation in the LCS click on the authorize link. Linking LCS to Azure subscription click on the Add option and set the required option make sure the subscription id is same as you have in the azure portal as we may have multiple subscription set so keep in mind to use correct subscription. Once we fill the required details click on the next. Once we click on next we’ll required to authorize the user to the subscription or we can download the certificate and upload to the azure portal by going to the Subscription > Management Certificates > Upload then upload the certificate that we have downloaded. Select the server environment region for LCS. Now we can see the azure connection in the project setting we got Azure subscription id that is showing . Deployment for the virtual machine In newly created environment go to the Project and in environment tab click on the (+) sign Once we click on (+) sign we’ll application platform option choose the latest application and platform version. Select the environment topology here we are selecting Demo environment Specify the Deploy environment setting by clicking on the Advance setting option Choose the below option and leave the other settings as default Click on the next. We can set size of the virtual machine of our choice it’s fine to keep the default settings and go ahead. Once confirm and deploy the VM deployment will start, usually deployment will take 3 hr. So, this will create the D365 Operation Environment for us. In next blog we’ll see how to setup the post deployment configuration setting for the environment

Steps to Perform Transfer In in Dynamics 365 for Retail on POS Go to Picking and Receiving –> click on + icon and click Transfer In Select the store from where you want to transfer in, Delivery date and mode of delivery. Add or scan all the products and its quantity. Click on + icon to add more products to the transfer order You can save the products added by clicking on Save icon. The status of the order will be in Draft. You can continue adding products when it is in Draft state by clicking on + icon. Once you are done adding all the products click on commit icon. Once the order is committed the status will change to created and you will not be able to add products. Once the Order is created, the Order will reflect in the store from where the order is requested. Perform the following steps in that store. For example the warehouse. [Products can be shipped from Finance and Operations as well] Select the transfer In order and click the update icon. Click on ship all icon to ship the products. This will change the ship now column with values to ship. Then click on commit. This will change the status of the order to shipped. When the status is changed to shipped the same status will reflect in the store 101 as well. On store 101 User must click on the transfer order and click on update. Click on receive all icon and click on commit icon. This will complete the process.

Introduction: ERP solutions are complex and hence it is significant for any enterprise to analyse the necessity and extract the complete understanding of the solution so as to derive the full benefits of it internally before it decides to deploy one. Having said this, Microsoft Dynamics 365 is one such platform which rather offers a clarity on the solutions. Microsoft now offers two ERP based solutions on Dynamics 365 Platforms. D365 Business Central D365 Finance & Operations The companies planning to implement D365 ERP need to choose prudently which product will suit their business requirements or best, consult their IT partner for the same. Here is the table comparison of two products which will help the decision makers to take the right decision. I have listed down product features with a general comparison view so that it is easier to understand them in a better way. General Comparison: Product/Feature D365 Business Central  D365 Finance & Operations Multiple Legal Entities Yes Yes Intercompany Postings and Consolidated Statements Yes (only within same country/localization) Yes Complete ERP with – Finance (AR/AP), Manufacturing, Logistics, Inventory, Warehousing Yes Yes Supplier Evaluation Module No Yes Quality Management Module No Yes PowerBI Embedded for Analytics No Yes Dynamics 365 Talent (Core HR, Attract, Onboard) No Yes Dynamics 365 Sales with Integration to ERP No Yes Dynamics 365 Customer Service No Yes Dynamics 365 Marketing No Yes Dynamics 365 Social Engagement (Facebook, Instagram, Twitter, etc) No Yes Dynamics 365 Customer Satisfaction Surveys No Yes Dynamics 365 Customer Support Portal No Yes Mobility (Apps for iOS/Android) Yes Yes Browser-based (Chrome, Edge, Safari) Yes Yes Dev and Production Environments Only Production Yes Minimum User License requirement No Minimum 20 Licensing Cost (US $ per user/month) $100 $200  Module Wise Comparison   D365 BC D365 FOE General Customer Type Small to Medium Medium to Large Deployment Period Short Long   Financial Management Auto Elimination Accounting – Available Consolidation Available Available Budgeting Available(Basic) Available(Advanced) Budget Control – Available Fixed and Variable allocations Available Available Ledger Allocations – Available Fixed Assets Available Available Cost Accounting Available Available Multicurrency Available Available Financial Dimensions Available (Upto 8 dimensions) Available (Unlimited) Multi-company Available Available Multi language Available Available Bank Reconciliation Available Available Electronic Funds Transfer Available Available Global Chart of Accounts – Available Multiple Posting Layers – Available Supply Chain Management Sales Orders Available Available Returns Management Available Available Sales Tax Available Available Purchase Orders Available Available Requisitions Available Available Serialized inventory Available Available Bins Available Available Assembly Available Available Inventory Transfers Available Available Procurement and sourcing – Available Global Customer & Vendor – Available Global Products – Available Advanced Warehouse Management License Plate Tracking – Available Basic Warehousing Available Available Aisle, Rack & Shelf – Available Transport Management – Available Quality Management – Available Warehouse Monitoring – Available   Production Basic Production Available Available Process Based manufacturing – Available Lean manufacturing – Available Multi Plant & Multi Schedule Planning – Available Human Resource Employee Master Available Available Recruitment Process – Available Attendance – Available Payroll – Available Performance – Available Training – Available Skill Sets – Available Project Management Job Costing Available Available Project Accounting – Available Employee Timesheets Available Available Employee Expenses – Available Schedule Board – Available System-wide Capabilities Office 365 Integration Available Available Microsoft user interface Available Available Workflows Available Available Web/mobile client Available Available E-mail Integration Available Available Document Management Available Available

Issue : Database Sync Error while applying deployable packages or Updates. Usually the Database sync error occurs at step 11:GlobalUpdate script for service model: AOSService on machine: —- Follow the steps to resolve the issue and resume the deployment. In this environment, go to Environment Monitoring –> SQL INSIGHTS –> ACTIONS tab In List of Actions, choose “Drop index” In Parameters, input “I_6640RECID” and “BANKIBANCOUNTRYACCOUNTSTRUCTURE” in Index name & Table name respectively. Choose Execute to drop the index then resume deployment.  

Issue: Void Transaction Appears in show journal in POS for Dynamics 365 for finance and Operations 8.1 When the system is upgraded to dynamics 365 finance and operation version 8.1 the user will observe that all the void transactions appear in Show journal. This bug is resolved as “By Design” means this is the expected behavior to show voided transaction with return button disabled If the voided Transactions are being returned you need to apply the APPMU general application 8.1.2 update and this will resolve the issue! On application of this update the user will not be able to return the voided transaction.  

Introduction: In Dynamics 365 for finance and operations the default decimal point is set up till 2 decimal place. To change the decimal point according to customers wish follow the following steps. Steps: 1. In the development environment run the Visual studio in administration mode. 2. In AOT find the EDT of the field and change the No of Decimals Property to 4-6 depending on the customers requirement. 3. Compile and build the solution. 4. The changes will be visible on Dynamics 365 finance and operations.

Introduction: In this blog article, we will see how we can create Item Requirement on insertion of Item Forecast using code. Steps: Create Extension Class for ForecastSales Table that is Item Forecast and using CoC for post insert() method we will initialize Item Requirement. We will call a new class which is created in Step 2. public void insert() {     next insert();     SalesType salesType = SalesType::ItemReq;     CFSCreateItemReqFrmItemForecast createItemReq = new CFSCreateItemReqFrmItemForecast();     createItemReq.initParameters(this);     createItemReq.copyToSalesLine(SalesType); } Create a new class that will initialize values and insert record in Item Requirement form. class CFSCreateItemReqFrmItemForecast { ForecastSales forecastSales; }  In the new class create a method initParameter. This method will initialize ForecastSales object. void initParameters(ForecastSales _forecastSales) { forecastSales = _forecastSales; }  Create another method ‘copytoSalesLine’. It will validate the record and call other methods to copy values to SalesLine Table. public void copyToSalesLine(SalesType _salesType) { ProjTable projTable = ProjTable::find(forecastSales.ProjId); if (_salesType == SalesType::ItemReq) { if (!ProjStatusType::construct(projTable).validateWriteItemRequirement()) { throw error(“@SYS18447”); } } else { if (!ProjStatusType::construct(projTable).validateWriteSalesLine()) { throw error(“@SYS18447”); } } SalesLine salesLine = this.initializeSalesLine(_salesType, forecastSales, projTable); salesLine.createLine(false, // Validation false, // Init from SalesTable true, // Init from InventTable true, // Calc invent Qty false, // Search markup – copied from salesQuotationline false, // Search price – copied from salesQuotationline false, // Check reservation true); // Skip creditlimit check this.updateSalesLine(salesLine, forecastSales); salesLine.update(); } Create a new method ‘initializeSalesLine’. It is called from copyToSalesLine(). protected SalesLine initializeSalesLine(SalesType _salesType, ForecastSales _forecastSales, ProjTable _projTable) { SalesLine salesLine; salesLine.SalesType = _salesType; salesLine.initValue(); salesLine.setInventDimId(_forecastSales.InventDimId); salesLine.ItemId = _forecastSales.ItemId; salesLine.SalesQty = _forecastSales.SalesQty; salesLine.SalesUnit = _forecastSales.SalesUnitId; salesLine.ProjId = _forecastSales.ProjId; salesLine.ActivityNumber = _forecastSales.ActivityNumber; salesLine.CurrencyCode = _forecastSales.Currency; salesLine.initFromProjTable(_projTable, false); return salesLine; } Create a new method updateSalesLine(). It is called from copyToSalesLine() method. protected void updateSalesLine(SalesLine _salesLine, ForecastSales _forecastSales) {     _salesLine.DefaultDimension =       _salesLine.copyDimension(_forecastSales.DefaultDimension);     _salesLine.ProjLinePropertyId = _forecastSales.ProjLinePropertyId;     _salesLine.TaxGroup = _forecastSales.TaxGroupId;     _salesLine.TaxItemGroup = _forecastSales.TaxItemGroupId;     _salesLine.ProjCategoryId = _forecastSales.ProjCategoryId;     _salesLine.CostPrice = _forecastSales.CostPrice;     _salesLine.SalesPrice = _forecastSales.SalesPrice;     _salesLine.LinePercent = _forecastSales.DiscPercent;     _salesLine.LineDisc = _forecastSales.DiscAmount;     _salesLine.LineAmount = 0;     _salesLine.LineAmount = _salesLine.calcLineAmount();     SalesLineType_ItemReq::setSalesLineReceiptDate(_salesLine); }

Introduction: In this blog article, we will see how we can post the journal by using code. How to do? Create a new method and write below code. In this code you declare object of Class ‘LedgerJournalCheckPost’. This class will use journal buffer and post it. public void postJournal(LedgerJournalTable ledgerJournalTable) { LedgerJournalCheckPost jourPost; jourPost = LedgerJournalCheckPost::newLedgerJournalTable(ledgerJournalTable, NoYes::Yes); jourPost.runOperation(); }

Posting restriction feature allow to determine whether specific user or user groups can post only journals that they create. You can use Journal names for posting restriction setup. Navigate to  General ledger > Journal Setup  > Journal names. Select Journal names for which you want to apply Posting restriction. Click on Posting restrictions button To set up posting restrictions by user group, select By user group.Select the check box next to the user group name. To set up posting restrictions by user, select By user. Select the check box next to the user name. Click OK to apply the restrictions and close the form.