In this blog article, we will see how we can export model in a model file, then import model file in development environment and delete existing model in development environment. Prerequisites: D3fO Environments. Steps: Export Model in a Model File. Import Model File. Resolve Conflicts. Build and Synchronize Model. Export Model To export a model in a model file, use the ModelUtil.exe tool which is located in j:\AOSService\PackagesLocalDirectory\Bin and the -export directive. ModelUtil.exe -export -metadatastorepath= [path of the metadata store] -modelname=[name of the model to export] -outputpath=[path of folder where model file should be saved] Example: Import Model To install a model file in development Environment, use the ModelUtil.exe tool and the -import directive. ModelUtil.exe -import -metadatastorepath=[path of the metadata store where model should be imported] -file=[full path of the file to import] Example: If the model already exists in Development Environment, then first delete the model using ModelUtil.exe tool and -delete directive. ModelUtil.exe -delete -metadatastorepath=[path of the metadata store] -modelname=[name of the model to delete] Example: Resolve Conflicts If the model you installed has customizations in higher layer, you need to resolve code or metadata conflicts. Under Dynamics 365 -> Addins -> select Create Project from Conflicts. In dialog box, select the model you installed, to check for conflicts. Click Create Project. New Project is created with elements having conflicts. Resolve the conflicts. Build and Synchronize Build the Model and Synchronize the Database.

This article is about the issue faced while publishing an extension in NAV 2017 which was resolved after the new CU 1 release of NAV 2017. Pre-requisites Microsoft Dynamics NAV 2017 Windows PowerShell ISE/ Issue faced in previous version 10.0.12762 of NAV 2017 In our extension, we had created a function which runs a report. The property ‘ProcessingOnly’ of the report was set to yes. This property when set to ‘yes’ deletes the report layout. While publishing the extension using Windows PowerShell, I encountered an error “Cannot find Report Directory”. Issue Resolution after CU 1 release of NAV 2017 version 10.0.14199 I referenced blog written by ‘Amol Salvi’ which describes Cumulative Update Released summary. I installed the cumulative update 01 (CU 1) for Microsoft Dynamics NAV 2017 (Build 14199) and published my extension using Windows PowerShell which was successfully published.  

Introduction We implemented Packing Requisition functionality for one of our Pharma Client in NAV 2016. The same functionality is replicated in NAV 2017 using Extension. Client Requirement The client process is such that once the goods are produced it needs to be packed as per the instructions given by the customer. These packing details needs to be send to customer and  to other parties like Shipping Agency and Customs Department. The packing details needs to be stored in the system for reference as well as for preparing some shipment documentation. The details are also useful to identify the batch number and expiry date of goods packed in particular shipper along with the gross weight and net weight. Pre-requisites: Microsodt Dynamics NAV 2017 Windows Powershell ISE Purpose In NAV, after a Sales order is created there is no provision to enter packing related details . Once the goods are produced it is directly shipped. Thus to fulfill the client’s requirement we developed the Packing List Functionality. Customization in NAV 2016 In NAV 2016 we can directly customize standard objects and can alter the source code. Customization in NAV 2017 with Extension. In NAV 2017 using Extension, we extend NAV without altering the standard source code. Extensions can be installed or uninstalled, giving customers compelte control over the additional functionality that they need. All coding with respect to adding of fields in NAV 2017 using extensions is done using the Codeunit object. In the Codeunit object, we create functions to trigger on insertion, modification,validation of that particular field. In the properties of the function,we subscribe to the system Event and specify the Event Publisher Object. The Event Function ‘OnAfterValidateEvent’ is selected from the lookup and the Event Publisher Element is selected. Steps We create Packing page which should have Sales order number, customer details and shipping information. The Packing sub form is then created having details like product type, description ,total quantity.Packing Case details Page which would be the sub page of Packing Sub form having details like number of cases, the gross and net weight, batch number, manufacturing and expiry date. The following are the steps to implement the packing functionality in NAV using extensions. We create folder as below and all original objects to be modified are first exported in the .txt format in the Original object folder. The below modified objects for the extension packing requision functionality are exported in .txt format in the Modified Folder. A menu suite is created which consist of the link to the packing list page in the Order Processing Department. Now we import all the unmodified objects and all the newly created objects are deleted. We then run Windows PowerShell ISE as Administrator, create delta file by using ‘Compare-NAVApplicationObject’ commandwhich consist of only the modified objects. We Specify the paths of the folders and run the command. The manifest file is created using ‘New-NAVAppManifest’ command which consist of the publisher name, version number and extension name in a .xml format. The navx package is created using the ‘New-NAVAppPackage’ command in .navx format The .navx package is published using the ‘Publish-NAVApp’ command The app is installed using ‘Install-NAVApp’ command. Test the extension by running RTC In Sales and Marketing select sales and receivable setup, and enter the package No. series. The Customer No. is selected from the lookup and the customer details are auto populated. We enter the product details in the sub form. The No. In the packing is sub form is selected using the lookup and the related fields of the product are auto populated. Clicking on Line of the Packing sub form we enter the packing case details. Conclusion. In NAV 2017 using Extension, we extend NAV without altering the standard source code. Extensions can be installed or uninstalled, giving customers complete control over the additional functionality. A packing list functionality provides information about the the sales order, customer,shipment information and Shipper’s details of the product.  

In this blog article, we will explain about the new updates of Power BI related to Date Slicer, Top N Filter and Data label improvements. In Date slicer, earlier there were only one option to show the data i.e. list. But now we have four option as before, after, between and list. Means we will show data by choosing the date range as between, after, or before selected date. Also, we can move the slider to set date. Date Slicer: While using date slicer we can use either slider to set the dates or pick the date using a calendar or also we can manually insert date: – The following are the four option that we can choose on date Slicer: Between Before After List We can change the mode to before or after if we only need to control the last or first date used on reports page. Or also we switch back to the standard List view Top N: Earlier we had only two filtering condition these are Advanced filtering Basic filtering But now there is one more option i.e. Top N By using this filtering condition, we can display the Top or Bottom N records. We will find the top N filter in the filter pane as a filter type option for the category field we want to filter down. Top N filter is use to retrieve the top or bottom N records. In this we can specify the numbers of items to show or display. For example:  select Top or Bottom from option set and specify value as 10 Then it will retrieve Top or Bottom 10 records from the table with specified value. Data Label improvements: In data label, there added several new data label capabilities to column, bar and waterfall charts to help our design for our visuals with labels. For column charts, now we have the option to change the orientation of the data labels between horizontal and vertical. This will help to fit longer data labels when we have skinnier columns. Also for column, bar and waterfall charts we can change the position of the data labels. We have the following option to set the position of data labels: – Inside End Outside End Inside Center Inside base  

We have a requirement that we want to change button text and description for case entity to the incident. Since the case is system entity which is managed, dynamics 365 not allowed you to make any modification in button text or description. For the unmanaged entity, you can make a modification with the help of third party tool like ribbon workbench. In this article, we will see how to change button text of system entity (managed). Kindly follow below steps. Create a new solution and add selected entity in that solution. In my example, I want only case entity. Make sure you have checked “include entity metadata”. Click on export translation The zip file will be downloaded to your system. Extract that zip file in your local system. Open CrmTranslations file in excel Select Display String sheet Find text that you want to replace. I want to replace all case word with incident. Make necessary changes and save the file. Again zip CrmTranslations folder and click on import Translation. Import zip file to the solution Publish the solution and go to entity form. You can see button text and description changed to the incident. Similar way you can do it for another system (Managed) entity.  

In this blog article, we will explain you on how to connect dynamics 365 financials service inside of Power BI. Earlier Microsoft dynamics 365 gives out of the box connectors for Sales, service Manager and Marketing to connect over Power BI for readymade dashboards but on the new powerbi updates we have direct connector for Dynamics Financial 365. Below are the steps to connect over Financial OData: Open the Power BI desktop tools and clicked on getdata Select “Dynamics 365 for financial” in Online services. When Promoted, enter your Microsoft Dynamics Financial OData URL For getting this ODAT URL, you need to first login on dynamics 365 portals and then search web services in the search button, so you get below screen and copy the OData url. Please use url up to “OData” flag only. After connecting this ODATA URL, it will ask for the authentication so choose basic authentication Mode and your User Details. Your password is the web service access key of the Admin user and you can get it from users tab. So, after connecting to the financial ODATA you will get all the tables loaded in to powerbi desktop tools and from that we can design a dashboard.  

In this blog article, we will see how we can create a Project and Deploy a Dynamics 365 Operations Environment using Microsoft Dynamics Lifecycle Services. Prerequisites: Lifecycle Service Account Azure Subscription Steps: Create a new project in Lifecycle Service Account. Azure Settings Deploy Environment. Create New project in Lifecycle Services Navigate to https://lcs.dynamics.com/Logon/Index Click Sign in. Loginwith the account you used to subscribe. Click the + icon to create a new project. Select the project type- “Migrate, create solutions and learn Dynamics 365 for operations”. See below screenshot for reference. Enter the project information and then clickCreate. Azure Settings: Follow this link to setup your Azure connector settings, https://ax.help.dynamics.com/en/wiki/arm-onboarding/ Deploy Environments: In newly created Project, go to Environmentssection, click the plus sign (+). Refer screenshot below You can click either the Downloadlink to download the VHD or Next to deploy on Azure. Azure is the preferred path. Enter the environment name. Read the terms, and then select the check box to indicate you understand them. Click Next. Confirm the details, and then click Deploy. So, this will deploy the D365 Operations Environment. Let me know your reviews. I will soon come up with more articles, as I further explore D365 Operations.  

Auto Capture is a feature introduced in D365 so that you don’t need to go to your Outlook and explicitly tracked Emails to Dynamics 365. This is one cool feature that can help you poll your personal emails and show you if you want to track it or not! Overview Auto Capture is a sub-feature of Relationship Insights. Relationship Insights is a preview feature in December 2016 update for MS Dynamics 365 Online. Integrates with Microsoft Exchange to find and display relevant emails with other activities that are related to a given record in Dynamics 365. Auto Capture shows you message in private i.e. only to the logged in user. System Administrators too don’t see these emails. Server Side Synchronization must be enabled to use this feature. Enable the Preview Since this is in preview, you’ll need to enable it for the organization in the following manner: Navigate to Settings > Administration > System Settings. Go to the last tab, Previews. Agree to the terms on the top and scroll down to the very bottom. Select Yes for the Enable Auto Capture feature as shown below: Then, navigate to Settings > Relationship Insights. You can choose the same and agree to the terms as shown: Upon agreement, you’ll see the three tabs as shown below: Make sure the Turn on Auto Capture for your organization is already checked. If not, check it and Save the same. Auto Capture has now been enabled for your organization. Auto Capture Auto Capture messages are queried to your Microsoft Exchange account every time you open the Activities section of a record. Once this has been enabled, you can navigate to different records like Accounts, Contacts etc. and see under Activities that certain emails which are relevant to the record you are viewing have been polled and are marked with dotted border: This email is only visible and is not yet tracked into Dynamics 365. It will be tracked only once you chose to do so. You can track this email in Dynamics 365 by hovering over the email in Activities and you’ll see a TRACK link on the same as shown below: Once you click on track, the Email will be queued to pull in Dynamics 365. Once the email is successfully tracked, it will appear like a usual Activity item shown on the form under Activities: This email can then also be seen in the Activities in Dynamics 365. What Messages are captured? Below are the criteria for polling messages from your Exchange Account.  

TIBCO Cloud Integration AX Connector is compatible with Dynamics 365 Operations. Connecting to D3fO is similar to that of Microsoft Dynamics AX. Prerequisite: Dynamics 365 Operations Development environment. TIBCO Cloud Integration Subscription. Global admin credentials in Azure: Registering ERP application in Azure. Steps: Login to TIBCO Cloud Integration URL: https://app.scribesoft.com/ Create a new connection by selecting the connector type as Microsoft Dynamics AX. Fill in the required details. OData Service URL: This URL must end in /data. Process to get the Client Id and Authentication URL. Steps: Login to Microsoft Azure URL: https://portal.azure.com In the left navigation bar, select Azure Active Directory Select App Registrations Click on Add. Fill in the details. Enter the name of the app. Select Application Type as Native Redirect URI: https://login.microsoftonline.com/domainname.com This redirect URI is the Authentication URL required in TIBCO Cloud Integration AX Connector. On creation, the registered app details will be displayed The Application ID in the Registered app is the Client Id required in TIBCO Cloud Integration AX Connector. Click on Required permission in the settings. Click on Add Select Microsoft Dynamics ERP (Microsoft.ERP) Select all three Delegated Permissions. For more details, check this link. Click on Grant Permission. Global Admin credentials are required for the same.  

Introduction This blog resolve a scenario requested by client to display Status Reason conditionally on Case entity. This requirement can be fulfilled by using Transitions functionality on Status Reason field on Case entity in D365 Sales. Steps of Implementation Open Status Reason field on Case entity Click on Edit Status Transitions and check the checkbox for Enable Status Reason Transitions. Select New Status Reasons for Current Status Reasons by clicking ellipses button After selecting values and click OK button. Click OK on Status Reason Transactions page Click OK on warning message Click Save and Close button on Status Reason field Publish All Customizations from Solution and Status Reason are displayed conditionally as seen below. Note: “Edit Transitions in Status Reason” functionality is only available on  Case and Custom Entities.