One of the most dynamic and popular ERP systems among mid-sized organisations is microsoft dynamics nav integration. This is popular for its easy installation and super easy and understandable interface which literally anybody could learn within no time. It is the most needed system for the retailers where it controls your financials, supply chain, business intelligence and much more.  As retailers grow though. the need for integrating their NAV ERP becomes evident. Your ERP isn’t the only system needed to run your operations. Retailers must share the same data between their POS, eCommerce, marketplace, 3PLs, and other important systems. Integrating Microsoft NAV with other retail systems is no small task. To get you started, we put together this beginner’s guide so you can learn all the basics when considering integration. Introduction: Automated Clearing House (ACH) payments to vendors can be done through Microsoft Dynamics NAV. To do ACH payments, setup is required to be performed basically in four areas: Company information, Bank Account card, Vendor card and Vendor bank account. Pre-requisite: Microsoft Dynamics NAV 2017 (North America NA version) Purpose: In this blog, I will be covering the setups required to perform ACH payments to vendor bank accounts in NAV. Procedure: Step 1: Navigate to Company information card and enter Federal ID No. Step 2: Navigate to Bank Accounts and select the bank from which payment will be done to the vendor. Enter following fields in the bank account card 1. Bank Branch Number 2. Bank Account Number 3. Last Remittance Advice No. 4. Export format: Select from given three options i.e. US, CA (Canada), MX (Mexico) 5. E-pay Export File Path: Enter the path where you want the export file to be saved which will be transmitted to the bank. End the file path name with ‘\’ 6. Last E-Pay Export File Name: Enter a name of the file with numeric value as the last digit to the right and the extension. The first file name which will be saved will be incremented by 1. 7. E-Pay Trans. Program Path: Enter the path of the transmit folder. When user selects transmit in payment journal, NAV moves the file formed in Export folder to Transmit folder. End the file path name with ‘\’ 8. Transit No.: Enter the Transit number of the bank which is the bank’s routing number. Step 3: Navigate to the Vendor card and perform the following steps. I have created a new payment method code i.e ‘ACH’ so that it is easy to differentiate vendors that use ACH as their method of payment from vendors that accept checks. Select ‘ACH’ as the payment method code. Now, navigate to the Vendor’s bank account. Enter following fields in vendor’s bank account. 1.  Vendor’s bank branch no. 2.  Vendor’s bank account no. 3.  Vendor’s bank transit no. Select the ‘Use for Electronic Payments’ checkbox to enable ACH payments for this vendor. After filling in these fields, select the preferred bank account code in the vendor card. The above mentioned steps are the setups required to perform ACH payments to vendors in NAV. I will be covering the procedure required to export and transmit the payment file which is generated while doing ACH payment to vendors in my next blog.

Introduction: Recently, I had encountered an issue with embedded images in a report. I had one image in two format, i.e. PNG and JPG. In the report viewer, both the image format was working fine; but when I saved the report in PDF format, PNG image was properly displayed and JPG image was distorted. In this article, we are going to discuss how to resolve the issue of distorted image in PDF. Images in Report Viewer: Images in PDF: Resolution: 1. Check JPG Image properties: Images with following properties do not render correctly: Image with CMYK Colorspace or Image with extended color profiles or Both For more reference, Click here Check Extended color Profiles Photoshop CC: Open the JPG file in Photoshop and it will tell you if the color profile is missing or does not match your working profile. Jeffery’s Image Metadata viewer: Open link: Jeffery’s Image Metadata. Choose your JPG Image file and click on View Data. Check Color Embedding. (Here, unrecognized embedded color profile) Check Image Colorspace Photoshop CC:  Open the JPG file in Photoshop, you can see the image properties in the Name Tab. (Here,CMYK/8) Jeffery’s Image Metadata viewer: Open link: Jeffery’s Image Metadata Choose your JPG Image file and click on View Data. 2. Change JPG Image Properties: Remove Extended color Profile: Open the JPG file in Photoshop. Navigate to EDIT→Assign Profile→Don’t color Manage this Document. Change Image Colorspace: Open the JPG file in Photoshop. Navigate to IMAGE→MODE→ RGB Color Results: After the change in image properties the JPG Image will be properly rendered in a PDF.

Microsoft Dynamics CRM Sales Process aims to generate potential sales opportunities and gives a new lead and boost to your business. It is intended to help the business procedure from gaining another lead through the end of a deal and to create exact deals gauging. Via mechanizing and enhancing a few phases, it smoothes out the business procedure while improving the pace of the conclusion. It additionally helps track and measure each deal’s action and see each number and segment of the business pipe so as to develop pay. Utilizing the Dynamics CRM deals process, you can focus on the correct leads and construct a remarkable deals pipeline. The CRM sales process ultimately increases the revenue of a company which every organisation aims in doing by supporting the business from beginning to end Introduction: With CRM 2016, Dynamics added controls which can be used in Phones, tablets and some on web forms as well. One such important control is the signature control in Dynamics CRM. This control is available for Phones and tablets, and very important in the modern sales process. In this blog, we will see how to add Signature control on Mobile and Tablet forms. Steps: Create a Multi-line text field with minimum length greater than or equal to 15000. Let’s say the name of the field is “Customer Approval” Add the Customer Approval field to CRM form. Add the Pen Control on the Customer Approval field. Once you publish, you can now see this control on your Mobile and Tablet application. It will look like below. Note: You also need to select the check box below the signature for the app to save the data. Once Customer/ Person signs using the above, the information is stored back in CRM. Other Information: The control cannot be used on Web forms. It will look like a Text box field. So, it is advisable to have this field locked or hidden on Web. On web form, and in CRM DB, the data is stored as the base64 format inside the field. So if you open the form on CRM, it will look like below. Conclusion: Using controls for forms on mobile, and tablets vastly improves the user interface on handheld devices. It is important to understand controls and apply them at relevant places on CRM forms. PS: I will be writing another blog, which will automatically convert the base64 data of the signature and store it as an attachment on the entity.

Introduction: This blog explains how to hide custom buttons on create form in D365. Problem Statement: We often get requirement from Client to hide custom buttons on Create record and to be shown on updating of record. Solution: We can achieve this functionality by having ribbon Customization with Enable Rules using FormStateRule. Steps of Implementation: 1. Create a new Command. 2.  Create a new Enable Rule. 3.  Create a new FormStateRule. 4.  Set Enable Rule on Command. 5.  Set Command on Button. Conclusion: Below image confirms button is hidden on Create Record and it is shown on Update Record. Create Record: Update Record:

Introduction: In this blog, we shall see how can a user create an Entity List OData Feed using custom JavaScript in CRM Portals. Pre-Requisites: D365 CRM Portals D365 CRM Environment Why Use OData (Open Data) Protocol? OData provides external access to a data source via a website. Recommended for the Open Government Data Initiative. Data API for Microsoft Azure Data is delivered in JSON format unlike XML format. Use of OData for custom live reports, new feeds, external applications, or leveraged by client-side AJAX for unique Entity List UI. Scenario: In the following scenario the user will learn how to configure an Entity List OData Feed and Configure OData Display Using Client-Side JavaScript. The following below image shows the OData feed from an Account Entity List, that we are going to create using client-side JavaScript. Fig 1. The OData to be configured using client-side JavaScript Steps for Implementing Above Scenario Step 1: The user will have to first create a new ‘Entity List’ in this case a ‘Account’ Entity List by going to Portals>Entity List and click on ‘New’ and in the Entity Name input select ‘Account’ and create a view Name “Active Accounts” that will display a grid view of all the Active Accounts as shown below in the following two images. Fig 2.1 Creating a New Entity List Fig 2.2 Setting Properties for the Entity List Now, user will have to enable the Entity List for OData Feed by checking on the ‘Enable’ option and entering the details into the input fields in the OData Feed Section for the Entity List as shown below: Fig 2.3 Setting Properties of OData Feed for the Entity List Step 2: The user will have to create a Page on the CRM Portals to display the following Entity List. The user will have to use the Admin panel and click on ‘Child Page’ to create a new Page which will display the Entity List after setting the properties of the page as shown below. Fig 3.1 Setting Properties for the Portal Page that will display the Entity List Fig 3.2 Setting up the Account Entity List Page Step 3: The user will now have to obtain the OData Feed by entering ‘/_odata’ to the end of the Portal URL that the user uses to open the CRM Portals which will open a XML page as shown below. Fig 4.1 OData URL of the CRM Portal Note:  The user will have to save the odata xml format and open it in another application like ‘Notepad’. Fig 4.2 XML Format of the OData Feed on CRM Portals Now in the above XML format we can see that accounts is being used as the href. To obtain the JSON format of the OData Feed the user will have to add the href used in the XML format to the end of the previously seen OData URL which is shown below. Fig 4.3 URL to obtain JSON format of the OData Feed Fig 4.4 JSON Format of the OData Feed on CRM Portals Note: The user will obtain a URL to the bottom of the JSON Format of the OData Feed which will provide the user to go to next set of records for the Entity List Step 4: Once the user has obtained the OData Feed the user will have to render the following OData Feed with a unique UI provided by ajax JavaScript on the client Side. The following is the Custom JavaScript containing the ajax call function against the OData Feed as shown below. Fig 5.1 Custom JavaScript to display OData Feed on CRM Portal Page The user will have to paste the code into the source code of the CRM Portal Page as shown below to which he wants to display the OData Feed as shown previously in the Scenario above and click on Save as shown below.  Fig 5.2 Pasting the JavaScript into the Source Code Conclusion: In this way the user can implement a simple Entity List OData Feed on CRM Portals using a client side custom JavaScript.

In this blog article, I will explain you on how to Embed POWER BI reports inside of your custom web app. Below are the steps to connect over Power BI Embedded: Create the Workspace collection inside of azure portal Stored PowerBi access key for the workspace Workspace creation using Rest API solution file (download from github) Import powerbi pbix file on the same workspace ID Deploy embedded page using visual studio Iframe the  web page url insdie of your web app Let’s walk through the steps to build a Work space Collection using the Azure Portal. Open and sign into Azure Portal. Click + New on the top panel. 1.    Under Data + Analytics click Power BI Embedded. 2.    On the Work-space Collection Blade, enter the required information. For Pricing, see Power BI Embedded pricing. 3.    Click Create. The Workspace Collection will take a few moments to provision. When completed, you’ll be taken to the Work-space Collection Blade. So from this window please copy work-space collection Name and Subscription ID in the notepad for further use. We also need to copy PowerBI API access key for this workspace collection.       Now we need to generate workspace report and dataset using visual studio solution file which you can download from github. After downloding the file you need to ope “PowerBI embedded” soln file. In the solution file you can found 2 projects, Provision Sample: Used for build-up workspace and import pbix file to azure workspace collection EmbedSample: After importing PBIX this project used for deployment of web page url First we need to run the Provision sample project,It will generate one CMD window when you are going to run it. Here you can find different option for the activity, we already done with workspace collection name inside of azure portal so now we need to choose step 5 for creating workspace. Once you select step 5 it will ask for “Workspace Collection Name” and we need to type exact name which we created in azure portal. After that it will ask for access key and that key is your POWERBI API access key which we copied earlier. After this steps you need to select option 6.” Import PBIX Desktop file into an existing workspace” in the above cmd window. Now it will ask for Dataset Name and path of the PBIX file which you want to embedded inside of Web APP.Datasetname should be any user-friendly name for your reports. And it start importing our PBIX file into azure workspace collection. After succeeding this process, we need to select embed sample project inside of visual studio and required to change some information inside of web config file. Based on the above image we need to provide couple of information inside of web config file. Access key: it is POWERBI API Access key which created on azure porta Workspace Collection: Name of the Workspace collection we created in step 1 Workspace ID: this id you will get on cmd window when doing step 5 So, after doing this changes we need to run this project file and it will open new browser window with Power BI embedded reports inside. You can copy that url and iframe it inside of your Web APP. It will look like below:      

In this blog article, I will explain about the new updates of Power BI related to New Matrix Visual Preview and its enhancements. In these we introduce a preview of a new matrix visual. This is the new version of the matrix as a separate matrix visual so we can test out the new experiences without impacting any of our other visuals or Reports.   Benefits of this new matrix include: Performance improvements Drilling into hierarches Stepped layout Cross highlighting and filtering from matrix headers and cell contents In the new matrix preview, we can Go to next level in the hierarchy Expand all down one level in the hierarchy Drill Down When we create a hierarchy we will see only the top level by default and can drill into lower levels. We can drill into the row headers using the drill buttons in the visual menu or we can right click menu. Using the Go to next level in the hierarchy option we will move to the next level of the row hierarchy. Using the Expand all down one level in the hierarchy option we will show multiple row header levels at once. We can also turn on Drill Down and drill into one specific row header. We can also use right click menu to do all these drill actions on both row and column headers. In matrix visual we can Sort a column, Word wrapping and  resize the column width. i) Column Sorting We can sort the matrix visual by the total and row headers ascending or descending. ii) Column Resizing We can minimize or maximize the size of the column iii) Word Wrapping We can word wrap column headers, row headers and values in the matrix preview.

As an entrepreneur, if you want to streamline your operations and finance departments, you should go for an ERP solution. Countless companies are offering ERP or Enterprise Resource Planning solutions or software. Dynamics 365 for finance and operations, however, is one of the best ERP solutions that you can find in the market today. One of the key reasons why a lot of companies are using this software is that it is easy to install, configure, and to use. You can scale your business when you use ERP solutions like Dynamics 365. A lot of resources are available online that will help your employees become smart and efficient.  Deploying this software is easy. Here is some information for you In this blog article, we will see how we can deploy the package in Dynamics 365 Operations. This Package can be any latest update, hotfix or deployment package you have created. Prerequisites: LCS login VM Instance Steps: 1. Download, Extract and Unblock Package 2. Update topology configuration data 3. Generate a runbook from the topology 4. Execute runbook Download, Extract and Unblock Package a. Login to LCS and download the Zip file of Deployable Package. b. After downloading, go to downloaded Zip file properties and select unblock. c. Extract the Zip file to a non–user folder. Update topology configuration data a. Go to extracted folder and open the file “DefaultTopologyData.xml” b. Populate the file with VM name. i. Go to This PC -> Properties. Find the name of the machine. ii. Update the VM name with the machine name in the file. c. Populate the file with installed components i. Open a command prompt as an administrator. ii. Run the command from extracted folder path to see a list of all installed components on the computer. iii. Update the file with a list of components. 3. Generate a runbook from the topology a. Run the command to generate a runbook. AXUpdateInstaller.exe generate -runbookid=[runbookID] -topologyfile=[topologyFile] -servicemodelfile=[serviceModelFile] -runbookfile=[runbookFile] Example: b. Runbook will contain instructions in sequential steps to deploy the package. 4. Execute Runbook a. Import the runbook. AXUpdateInstaller.exe import -runbookfile=[runbookFile] Example: b. Verify the runbook. c. Execute the runbook. AXUpdateInstaller.exe execute -runbookid=[runbookID] Example: d. Export the runbook. Export the runbook for future reference, you can use it to refer the steps, time to execute each step and logs for each step. UpdateInstaller.exe export -runbookid=[runbookID] -runbookfile=[runbookFile] Example:

Microsoft Dynamics 365 for Retail Management Solution is the perfect answer to the questions from the modern day consumers related to cost-effectiveness, fast and flexible services that they aim for. Microsoft Dynamics aims at seamless management solutions across all retail channels making it easier for the customer to establish a balance between their business requirements and the deliverables. When it comes to power and performance, Microsoft Dynamics is the best enterprise resource planning (ERP) cloud solution currently available in the market This amazing retail management solution from Microsoft has considerably reduced the complexities faced by the retailers in their day-to-day life in a new and unified way making it one of the most wanted and demanded software solutions in the market. Introduction: Dynamics 365 Operation Retail is providing CPOS.  This Blog Describe you, how to configure CPOS in AX 7 Operation. CPOS is Online POS, Offline POS functionality does not support to CPOS. CPOS can be Open in Internet Explorer, chrome, Firefox browser. MPOS having Online and offline functionality. In this blog for Demo Purpose, we are configuring CPOS for Huston store. And for CPOS, I am using Chrome browser. Follow the Below Setup to Configure CPOS . Before you Start: Before you Start Configuration of CPOS. Go to the Retail and Commerce -> Headquarter setup -> Parameter -> Retail Shared Parameters Select Entity Validation Templates.  Click on Import Default template. After that Drill-down to template Option and select Select RetailVal and click on SAVE button. Step 1: Go to the Retail and Commerce > Channels > Retail Store > All Store And select Houston Store. Click on Configuration Status. Select Approve All and click on Update Button. Step 2: Go to Retail and Commerce > Channels > Channel Deployment In Retail Store search for Houston Store. You will find that Progress for Houston store is 100%. Step 3: Click on Registers. Next to that you will see all the register which is created all stores. Put the filter on “HOUSTON” on Store Number. After that you can able to view list Houston Store Registers. Select Registers Number “Houston-30” and Open it. Click on configuration Status Click on Approve all and click on Update. Once you click on Update. Status will change to Completed. Click on close button. Step 4: On register page click on Device Select “HOUSTON-30”. Application Type of this Device is “Retail Cloud POS”. which mean this is CPOS. Activation status is Pending and Validation Status is not Run. Change Activation Status from pending to Pending to Activated and click on Validate Devices for Activation. Step 5: In General Tab of Device “Houstone-30” copy POS URL and Past it in Browser. Or you can click on that URL Link. Click on Next Button. Server URL, Device ID and Register ID is set by Default base on your Cloud POS Device. Click on Activate button. Once you click on Activate, it will start for activating Cloud POS. Once its Active, you will get message Click on Get Stated. You can able to view Cloud POS Login Screen. Enter Worker user ID and Password to login. Conclusion: By following this Steps, you can configure CPOS in Dynamics 365 Operation.

Introduction: CRM SDK provides a data migration tool/application called “DataMigrationUtility” which allows simple data migration from one CRM environment to another CRM environment. Prerequisite: Microsoft Dynamics CRM. CRM SDK Purpose of the set up Our goal is to migrate accounts from one Online CRM environment to another CRM environment. Steps: Open CRM SDK folder and run ‘DataMigrationUtility’ application. Path: SDK\Tools\ConfigurationMigration Click on Create Schema. You’ll be asked to log in to your source CRM system. Select the solution, entity and fields. Then click ‘save and export’, this will save a XML schema file. To export data: select XML file created in the above steps and create a file to save the data (zip file); then click Exportdata. Click exit after successful export of data. To import data: Click on Import data and then continue. Login to your target system. Select Zip file which was created in the above steps. Click on Import data Error logs can be viewed from Logs stored.