Introduction: “Deprecated” means Microsoft intends to remove the feature or capability from a future major release of Dynamics 365. The feature or capability will continue to work and is fully supported until it is officially removed. This deprecation notification can span a few years. After removal, the feature or capability will no longer work. Microsoft notifies the Customers and Developers well in advance so that they have sufficient time to take action and update the code. Consolidated list of Deprecated Features in July 2017 release of D365 for Customer Engagement: Click on each of the link for details on Microsoft Official documentation site: Dynamics 365 for Outlook (Outlook client) is deprecated Service scheduling in Dynamics 365 for Customer Service is deprecated Dialogs are deprecated Usage of Parature knowledgebase as the Dynamics 365 knowledge management solution is deprecated Project Service Finder app is deprecated Contracts, Contract Line Items, and Contract Templates entities are deprecated Standard SLAs in Dynamics 365 for Customer Service are deprecated Relationship Roles are deprecated Mail Merge is deprecated Announcements are deprecated Ready-to-use business processes available through Add Ready to Use Business Processes setting are deprecated Some client APIs are deprecated – Details of APIs deprecated with their replacements in the link. EntityMetadata.IsInteractionCentricEnabled property is deprecated Silverlight (XAP) web resource is deprecated We will keep posting more on the details and alternatives for each feature above.

Introduction: In this article, we will see how we can generate Excel Report in SSIS without doing Physical mapping. Steps: 1.    Create Excel file with one data connection in the Excel Sheet. 2.    Create a sheet in Excel pointing to the data connection. This will lead to point the connection to the data source, and help create a table in Sheet. As soon as ok is pressed, the data from the connection is pulled. We can save this Excel as a template and next time we just need to refresh the connection and the data will be refreshed in the Excel Sheet. This is the day to day process which requires manual effort, WHAT IF WE CAN AUTOMATE THE REFRESH. It is possible through SSIS services, and Microsoft Interop libraries. Steps: 1. Create a SSIS package with a Script task with C#. Edit the script and include the following code in the Script task Use below script to refresh the data in the Excel. We need to include the reference for the Interop libraries. using Excels = Microsoft.Office.Interop.Excel; string filepath = @”D:\Excel Files\Employee Files.xlsx”; Excels.Application xlApp; Excels.Workbook xlWorkBook; Excels.Worksheet xlWorkSheet; object misValue = System.Reflection.Missing.Value; xlApp = new Excels.Application(); xlWorkBook = xlApp.Workbooks.Open(filepath); xlWorkSheet = (Excels.Worksheet)xlWorkBook.Worksheets.get_Item(1); xlWorkBook.RefreshAll(); xlApp.ErrorCheckingOptions.NumberAsText = true; xlApp.DisplayAlerts = false; xlWorkBook.Save(); xlWorkBook.Close(true, misValue, misValue); xlApp.Quit(); releaseObject(xlWorkSheet); releaseObject(xlWorkBook); releaseObject(xlApp); Benefits: 1. This process is used if we need to generate custom reports. 2. We can use the existing data in excel sheet to create pivot table, and create custom data formats. Feel free to contact us if there is any issue.  

Introduction: While working with Microsoft Dynamics CRM we wanted to make query or advanced find to list down all the account which does not have any opportunity associated to it. But in the dynamics CRM with current or earlier version we cannot write down the simple advanced find query which list down the record does not associate to it. Description: With upcoming update of Microsoft Dynamics 365 CRM, you can perform the Search on that criteria as well. You can design this query in the advanced find. Query: Get all the account which does not have any opportunities. 1. Open advance find and select account entity and in filter select opportunitie in related entities, as show below. 2. You will notice that a new attribute has been added, by which you can apply additional filter on opportunities. 3. Here you need to select the “Does Not contains data”. 4. Now click on result. 5. It will list down all the records which does not have any opportunities as shown 6. Fetch XML: let see what modification has been done in the fetch XML <fetch version=”1.0″ output-format=”xml-platform” mapping=”logical” distinct=”true”> <entity name=”account”> <attribute name=”name” /> <attribute name=”primarycontactid” /> <attribute name=”telephone1″ /> <attribute name=”accountid” /> <order attribute=”name” descending=”false” /> <link-entity name=”opportunity” from=”parentaccountid” to=”accountid” notinvalue=”DoesNotContain” link-type=”outer” alias=”af” /> <filter type=”and” isnotinfilter=”true”> <condition entityname=”opportunity” attribute=”parentaccountid” operator=”null” /> </filter> </entity> </fetch> 7. As you can see that it has an addition filter attribute is added. Query: Get all accounts contains opportunities. 1. Similarly, you can get all the accounts which have opportunities associated to it. 2. Here you need to apply filter criteria as contains data; as shown below. 3. It will list down all the account records with opportunities as shown below. Conclusion: Hope this helps while doing advanced find or designing fetch Xml query.  

D365 Field Service has everything to manage your complex business needs from scratch till the end. On the off chance that Field Service is a fundamental piece of your everyday business, Dynamics 365 for Field Service is a start to finish arrangement that can enable your association to oversee complex assistance understandings, track resources and stock, oversee administration orders, rapidly distinguish and dispatch assets, and addition the insight expected to offer prescient and preventive assistance and backing.  Robotize and improve booking to dispatch the correct professional and get the most incentive out of your assets. Upgrade your administration experience by proactively recognizing, investigating, and settling issues so a specialist is dispatched just when vital. Give clients self-administration entries, proactive updates, and expert following to guarantee a positive involvement with each progression.  Introduction: This blog explains how to embed D365 Field Service Charts in D365 Online Portals. Steps of Implementation: 1. Get Guid of Chart and View used for Chart in D365 Field Service. 2. Create a new Web Template, Portals -> Web Templates and write code in Source field with Chart ID and View ID  as copied in Step 1 as below. 3. Create a new Page Template, Portals -> Page Templates and set details as highlighted below. 4. Create a new Web Page in D365 Online Portals and set Page Template created in Step 3. 5. Create a new Link for Dashboard in D365 Online Portals. Hover Mouse on Home button and click on Edit option. Click on New button as highlighted below. Enter details as shown below and click on Save button. Conclusion: Above description in blog helps users to create Dashboard in D365 Online Portals by embedding D365 Field Service Charts as below.

Introduction: In this blog article, we will see how we can expose standard and custom data entities using OData Client code generator to OData API for CRUD operations. Steps: Install OData Client Code Generator v4 Create new Project Execute the OData Client code. 1. Install OData Client Code Generator v4: Open Visual Studio. Go to Tools -> Extensions and Updates Go to Online Fast Tab -> Visual Studio Gallery -> Type ‘OData V4 Client Code Generator’ Click Download. In the VSIX Installer dialog box, Click Install. After Installation, it will ask you to restart the Visual Studio. Click Restart now. 2. Create new Project: Click on new Project. Go to Visual C# -> Windows -> Select Console ApplicationNote: Client Code Generator can work with any project. Enter details and click OK. 3. Execute the OData Client code: In Solution Explorer, right click the solution. Go to Add -> New Item. Select OData Client. Click Add. You will see 2 files added in the solution. Open the file with .tt extension (Text Template). In the file, update the Metadata URI. Save and execute the .tt file. You can see a .cs file generated under the .tt file. Conclusion: This will generate a code that exposes all the Data Entities of D365 Operations. You can use this generated code for CRUD operations. In the next part, we will see how to use this generated code to read and write data in tables using exposed data entities.

Since this is in Preview, it won’t be available for users until next update. However, this is how it works and seems so easy to implement it. Enable Step Action from System Settings: Since this is a Preview feature in Dynamics 365 July 2017 update, it appears in the Previews section where you can go and enable the same. Once you’ve enabled the Preview feature, you should be able to see Action Step visible in the Business Process Flow editor as shown below: Add Action Step in BPF: You can trigger an Action or a Workflow in the Step Action feature. I have a Workflow to create a New Invitation entity record in D365. I’ll be adding the same in the BPF. In the Business Process Flow editor, I’ll add an Add Action Step in one of the stages as shown below: I’ll add the already created a Workflow to the Business Process Flow in the Step Action. Once done, I’ll simply activate the BPF and we can see it in action. Working with Step Action: Let’s see how easy it is to execute this workflow using the Step Action. On the Business Process Flow, I can see that the step appears from what the Display Name in Business Process Flow is set. And clicking on it, the workflow will run the background performing it’s operation. (You’ll see a quick ‘Processing’) message while it triggers the workflow. As seen below, the record for New Invitation was created as directed in the Workflow I created. Conclusion: Putting it simply, it works very quickly and is as simple as clicking a button.

Whether you are a small sized business, a mid-sized one or a large business, Microsoft dynamics nav upgrade is all you must do to gain new heights in your business. Elements NAV clients are passing up the genuine advantages of moving up to Dynamics NAV in the present cloud-based condition. Microsoft is persistently seeing approaches to ad lib the Enterprise Resource Planning Systems or ERPs.  In the event that you overhaul Dynamics NAV, you will be exploiting improved usefulness, new highlights, and upgraded abilities, you can help efficiency, diminish costs, and improve client assistance. Utilizing Microsoft Dynamics NAV Inventory Management, organizations can do errands, for example, setting up elective merchants, mind stock gathering the executives, and get the necessary investigation report easily. Introduction: To track changes that are made to records in a particular table and to store them sequentially in NAV, logs have to be created. Using logs we can record changes that are made to standard or custom fields in a table. In this article, I will be demonstrating the steps required to setup logs in NAV. Pre-Requisite: Microsoft Dynamics NAV 2017 Procedure: 1. Navigate to ‘Change Log Setup’ Page using the NAV windows or web client. 2. In the actions tab, choose ‘Tables’ under Setup group to select the tables and the fields on which changes are required to be logged. 3. A list of all the standard and custom tables will be displayed. Logs can be created on three events: Initially when the record is created, log will be created with the initial value of the selected field to be logged. When the record is modified, log will be created in the system with the old and new value of the selected field to be logged. When the record in deleted, log will be created in the system. 4. You can either select some fields to be logged or select the All fields option. If you select ‘some fields’, click on the ellipses (…) to select the fields on which log will be created. If ‘All fields’ has been selected, by default all the table fields changes will be logged. 5. I have created a log entry on ‘Item’ table on two fields ‘No.’ and ‘Car status’. Car status is a custom field with option datatype. 6. On clicking the ellipses (…) when ‘Some Fields’ is selected, the table field list will be displayed. Select the event when a log record has to be created i.e. Log Insertion, Log Modification or Log Deletion. 7. Now on the Change log setup page, select the ‘Change Log Activated’ checkbox. 8. After creating a record in ‘Item’ table and modifying the values of the ‘Car status’ field, the following logs are created in the system. Date and Time when the log is created is stored which will be useful to get history of events performed in the system at any point. The user ID who is creating and modifying records will be stored. Table caption stores the table name which is selected. Primary Key Field 1 Value stores the Item No. i.e. the unique field in the table. Type of change will be stored i.e. Insertion, Modification or Deletion. For option fields, the old value and new value is stored. Conclusion: These are the steps required to create logs in NAV which will track changes made to the fields selected in the change log setup.

Introduction: In this blog, we shall see how can a user install multiple Portal Instances for Microsoft D365 CRM Online. Pre-Requisites: D365 CRM Portals D365 CRM Environment Overview 1. A user can set up more than one Portal for a given D365 Environment provided that the second portal is different from the first portal that is installed. For eg: If the user has already installed a community portal then the user will have to install a different type of portal like partner portal , employee portal etc. 2. The user cannot install two portals of the same type. For eg. If the user has already installed a customer portal then he cannot install multiple portals which are customer portals. 3. As we know that a user can have multiple portals associated with the same D365 (CRM) instance and along with a single D365 Subscription the user gets out of the box a single portal license, which means that the user gets only one free portal add-on. 4. The user can go to the Instance page and install multiple portals as shown below in the available multiple options. In order to have a second portal add-on on the D365 instance the user will have to follow the Steps given below: Step 1: Opening the Admin Center.  Go to D365 and open admin as shown below. Step 2: Opening the Purchase Service In the Admin Center Page click on the Billing option in the left side menu bar and select Purchase Services under that. Step 3: Selecting the Subscription In the Purchase Services, we will have to find the following subscriptions which are as follows: Dynamics 365 Enterprise Edition – Additional Portal Dynamics 365 Enterprise Edition – Additional Portal Page Views **Note: These Licenses are only shown to the user if they have a purchased license and are not using trial version of the license

Introduction: Sometimes users accidentally can remove their emails from inbox and deleted items folder. You can find the deleted mail in Recover deleted items. There also might be a situation when a user cannot find a deleted email in their Office 365 mailbox, a user will probably ask you to recover missing mails. You can recover it directly through Exchange Online using the In-Place eDiscovery & hold options (You must be a Global Administrator in Office 365). Steps: To recover deleted emails, follow the steps below: 1. Login to your Office 365 account and go to the Admin app. 2. On Left pane, extend Admin centers and click Exchange (Exchange Admin Center). 3. Go to Permissions > Admin Roles. From list of roles select Discovery Management and click on Edit icon. 4. On resulting window, go to members section and click + to add a member. Search for your name and click add and Ok. Save it. 5. Sign out and Sign In again, so that changes take effect. 6. Once permission is assigned to you, go to the Compliance Management section and then In-Place eDiscovery & hold. Click + icon 7. Provide a name for your search and, optionally, a description. Click Next. 8. You can choose a mailbox you want to search. Select the Specify mailboxes to search option, and then click on the + icon to add a mailbox. Click Next. 9. The next step is to specify criteria for a search query. Click the Filter based on criteria option, and adjust search options to your needs. When you need to provide more than one keyword in a search query, you need to separate them with OR or AND, not commas. 10. In the same window, click on the Select message types and select Email. Click OK. You can similarly search for contacts, meetings, etc. 11. Once you adjusted search query to your needs, click Next. 12. In the In-Place eDiscovery and hold page click Next without choosing any options as we don’t want to place any content on hold. 13. Now, your settings will be saved. Once the process is completed, click Close. 14. Select the search you created and click Refresh to update the information displayed in the details pane. The status of Estimate Succeeded indicates that the search has finished. 15. In details pane, click Preview search results to view the items. This helps you identify the items you are looking for. 16. If you can’t find an item by previewing search results, then you can copy the search results to a special mailbox (called a discovery mailbox) and then open that mailbox in Outlook on the web to view the items. On the copy search results page, click Browse. Under the display name, click Discovery Search Mailbox, and then click OK and Copy (shown in above image). When the copying is complete, click Open to open the Discovery Search Mailbox to view the search results (shown in below image). The search results copied to the Discovery Search Mailbox are placed in a folder that has the same name as the In-Place eDiscovery search. 17. After you find the item you’re trying to recover for a user, the next step is to export the results from the search you ran to Export  to PST. The user will use this PST file in the next step to restore the deleted item to their mailbox. Click below arrow mark as shown in below image. 18. Click on Run to install eDiscovery tool. 19. Click on Browse button to add location and leave the enable deduplication & include unsearchable items option. 20. After providing PST location click Start, it will ask for Office 365 admin credentials, after providing the same download will start. 21. The last step is to just send this PST file to the user so that he can restore. User need to use the outlook desktop app to restore deleted item by using a PST file. Click to Open Outlook Data File, browse the file and click OK. The PST file appears in the left-nav bar in Outlook. Expand the same and right-click the item you want to recover and then click Move > Inbox. In the below image,  you can see recoverable items. Conclusion: You can easily recover the deleted mails of users even if it is deleted from deleted items and are not shown under recover deleted items.  

Introduction: This document contains the steps on how the TIBCO Cloud Integration Agent with custom connector for Dynamics GP can be deployed on server. Install a TIBCO Cloud Integration on-premise agent A TIBCO Cloud Integration agent needs to be installed on the server where the target data store resides. Download TIBCO Cloud Integration agent You can download and setup an agent from https://app.scribesoft.com Once logged in to TIBCO Cloud Integration portal in the server where the target data store resides, navigate to ‘More’ and then ‘Agents’ and then click on ‘+’ and ‘On-Premise Agent’ to create a new agent. Please refer the screenshot below: A new window will open where you can click on Install On-premise Agent to download the agent as shown below: On clicking Install On-premise Agent, TIBCO Cloud Integration will provide you to download the agent. You need to save the same to your local system. Copy the Agent Key in your clipboard; it will be used during Installation of Agent. Navigate to the location where the ScribeInstaller was downloaded and start the installation Make sure pre-requisites are setup to be able to successfully continue with the installation and click Next:   The wizard will start. Click Next until you see the screen where Agent Key is asked by the installer. Enter the same key which appeared on the screen where new agent was provided to be downloaded. And click next. Select where you want to install the TIBCO Cloud Integration agent. Finally click Install Agent. Let the setup continue. Click Finish once the setup completes.   Turning TIBCO Cloud Integration Agent on and off TIBCO Cloud Integration Agent on your system is a Windows Service which can be stopped, started and restarted. View Services application on your Windows machine to locate the TIBCO Cloud Integrationweb service Locate Scribe Online Agent in the Services. This is where you can start and stop service in the event of updating the DLLs for the Scribe Online connector. Deploying Scribe Online connector on the target system Deploying the Scribe Connector to the target system consists of copying the required DLLs and PDBs to the following folder in the Scribe Online Agent directory located on the target machine: Locate Connectors folder in the Scribe Online Agent directory. Folder named “DynAD Connector” contains DLLs and PDBs required to be available in the Scribe Online’s Connector folder. This folder needs to be copied in the Scribe Connector’s Connector folder. The address for Scribe Online Connector is: C:\Program Files (x86)\Scribe Software\Scribe Online Agent\Connectors Once the folder is pasted to the Connector folder, the agent needs to be started again. Navigate to View Local Services on the machine and locate Scribe Online Agent and start the same as shown below. For the Custom GP Connector developed for AKA, the following files are required to be copied in the “DynAD Connector” folder. Note: Since the project is divided into 2 DLLs across a Visual Studio solution, CFS.Connector.GPConnector.dll and CFS.GPClient.dll are the 2 DLLs and their respective PDDs are required. Required Files: Connector.GPConnector.dll and CFS.Connector.GPConnectorA part of the GP connector (.dll) and its PDD file GPClient and CFS.GPClientA part of the GP connector (.dll) and its PDD file Core.ConnectorApi.dllThis .dll file is required by the ScribeOnline agent to be able to access the Scribe API provided by ScribeOnline. Json.dll and Newtonsoft.Json These .dll files are required by the connector to be able to JSON file stream where the fields of the target connector are retrieved. JSON files – 5.1 DynADCampaignHeader.json 5.2 DynADCampaignLineItem.json 5.3 DynADSalesCommission.json 5.4. DynADCampaignErrorLog.jsonThe above files are the JSON files which contain the fields required by Dynamics GP entities. These files need to reside in the folder as the .dll require these. Important: These files also need to be present in the C:\Windows\System32 of the system. Updating Solutions with newly installed Scribe Online Agent Login to Scribe Online Portal through https://app.scribesoft.com Open a Solution and resign the Solution with newly installed Agent. Repeat this for all the Solutions. Conclusion: By following the mentioned steps, you can deploy the Scribe Online Agent with custom connector for Dynamics GP on server.