In this blog article, I will explain you how to deploy the  SSRS Report on SQL Server. Now you have your report done and it’s time to get them on your reporting server from visual Studio. Within Visual Studio, you can deploy your any individual report or entire project full of reports. In Solution Explorer -> right-click on your project -> Properties. Enter the Target Server URL. If you don’t know what your TargetServerURL is, Start instance of Reporting Services Configuration Manager  -> click the Web Service URL tab. The URL you need is in the Report Server Web Service URLs section. Return to the Property Pages box, enter the above URL as the TargetServerURL, and click OK. Now you can right-click on either your project or any single report and click Deploy. Now we have to verify that our report made it to the server and that we can execute them. To get the URL for previewing the reports, open the Reporting Services Configuration Manager, click the Report Manager URL tab and copy the Report Manager URL. Open that URL using Internet Explorer with administration permission(Right click on internet explorer -> run as administrator). Navigate to the SSSR Reports folder, click on your report name, and you should be able to execute it right there in the browser.

In this article, we see AX hotfix deployed by Scribe which resolves the issue for Update Patch in Dynamics AX Connector. Error Details: We have Integration build between Dynamics 365 and Dynamics AX. One of the Integration package integrates CustomerPostalAddress from AX to Address in Dynamics 365. In this package, we wanted to store AddressNumber of Dynamics 365 back in Dynamics AX. So, for updating the CustomerPostalAddress with AddressNumber we used UpdatePatch with AddresslocationId as the matching criteria. Unfortunately, we were getting an error as “Error in calling Operation Update Patch: Operation returned no results. Label: Update Patch CustomerPostalAddresses, Name: CustomerPostalAddressesUpdatePatch” Strangely, we could Query, Fetch and lookup using the same criteria of AddresslocationId to retrieve records from CustomerPostalAddress. Solution: Scribe recently deployed an AX hotfix which resolved this issue. Turns out, if any DateTime field is a primary key for a entity then in matching criteria we have pass all the primary keys. Here, we are using CustomerPostalAddress entity. Primary fields of this entity are: AddressLocationId (String) dataAreaId (String) Effective (DateTime) CustomerLegalEntityId (String) CustomerAccountNumber (String) So, in the Update Patch for CustomerPostalAddress we have to pass all these 5 fields for it successfully run the Update Operation.

Introduction: In this article, we will see how to resolve the below error while creating/quering records from NAV. Error Details: Error in calling Operation Query (Lookup Block): Operation failed. Label: Lookup CFSCar, Name: CFSCarLookup, Message: The following error has occurred in the Dynamics NAV Connector: Error: NotFound status code = 404. Resource not found for the segment ‘CFSCar’. Scenario: We have a scenario where we are building Integration Process between Microsoft Dynamics 365 (CRM) and NAV 2017. For NAV entities to be visible in Scribe Online, we have to create a Web Service in NAV for that entity. For more Information, you can check our blog article here. So, we had created a Web Service for Item entity i.e. here Items are Car details so the name ‘CFSCar’ in NAV. The ‘CFSCar’ Entity was visible in Scribe Online. But, recently we were getting “Resource not found” error for ‘CFSCar’ entity. So, we Reset the metadata for NAV connection in Scribe and the entity ‘CFSCar’ was not visible anymore. Troubleshooting: We checked the OData URL for entity ‘CFSCar’. We were getting the below error. Reading the above error, we couldn’t pin point the exact error, so we checked the SOAP Url as well. In the SOAP URL for ‘CFSCar’ entity, proper error was displayed. Error details: Naming Conflict within the “Car Status” object. Fields “Rental/Ops Hold” and Rental / Ops Hold” are both transferred to “Rental_Ops_Hold”. Please find new a name for one of those fields! Turns out there was two Status of same name which was causing an issue. Solution: Once we deleted the duplicate status the error was resolved.

Introduction: This blog explains how to filter Generic Type Bookable Resource on Schedule Board. Pre-requisite: Latest Field Service Solution of D365. Procedure: 1. Open Schedule Board, Field Service → Schedule Board.   As highlighted below there is no option to select Generic Type Bookable Resource in Filter Section. 2. Click Options → Selected Resources 3. Select Generic in Resource Types drop down as shown below. 4. Select Bookable Resources as per need. 5. Bookable Resource are shown in Schedule Board of type Generic. Conclusion: This blog explains how to filter Generic Type Bookable Resource on Schedule Board.  

Introduction: In this article, I will be giving the procedure to call an External API from Microsoft Dynamics NAV. The external API which I am going to call from Microsoft Dynamics NAV is ‘TIBCO Cloud Integration’ as I want to perform real-time integration between Dynamics NAV and Dynamics CRM. Pre-Requisites: 1. Microsoft Dynamics NAV 2. External API which will be called i.e. in this scenario, TIBCO Cloud Integration Mapping. Procedure: JSON syntax will be used for storing and exchanging data from Microsoft Dynamics NAV. I have created the following variables: ‘StringBuilder’ of datatype: DotNet and Subtype: System.Text.StringBuilder.’mscorlib’ ‘StringWriter’ of datatype: DotNet and Subtype: System.IO.StringWriter.’mscorlib’ ‘String Reader’ of datatype: DotNet and Subtype: System.IO.StringReader.’mscorlib’ ‘Json’ of datatype: DotNet and Subtype: System.String.’mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=***’ ‘JsonTextWriter’ of datatype ‘DotNet’ and Subtype: Newtonsoft.Json.JsonTextWriter.’Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=***’ ‘JsonTextReader’ of datatype ‘DotNet’ and subtype: Newtonsoft.Json.JsonTextReader.’Newtonsoft.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=***’ I have created a function ‘Initialize’ which upon calling will initialize StringBuilder, StringWriter and JsonTextWriter variables as below: StringBuilder := StringBuilder.StringBuilder; StringWriter := StringWriter.StringWriter(StringBuilder); JsonTextWriter := JsonTextWriter.JsonTextWriter(StringWriter); I have created a function ‘StartJson’ where I am calling the ‘Initialize’ variables function and then calling the ‘WriteStartObject’ of JsonTextWriter DotNet variable. Now create a function ‘AddToJson’ which accepts two parameters as below: The first parameter accepts the name of the Scribe field mapping   i.e. name of the External API field mapping. The second parameter is the field value which is passed from Microsoft Dynamics NAV. Create another function ‘EndJson’ and call the ‘WriteEndObject’ as below:       JsonTextWriter.WriteEndObject; Create a function ‘GetJson’ where the JSon content is converted ToString.       JSon := StringBuilder.ToString; Next I have created a function ‘UploadJSon’ which will upload and POST the parameter values from Dynamics NAV. The UploadJson has the following parameters: The Subtype of DotNet variable ‘String’ is ‘System.String.’mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=***’ WebServiceURL is the URL which will be called, in this case I will be passing the Scribe map URL which will be hit on a particular condition to perform real time integration. I have created two local variables for the UploadJson function as below: ‘HttpWebRequest’ variable of DotNet DataType and SubType : System.Net.HttpWebRequest.’System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=***’ ‘HttpWebResponse’ variable of DotNet DataType and Subtype: System.Net.WebResponse.’System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=***’ The following code is written in the UploadJson function: The CreateWebRequest, SetRequestStream, DoWebRequest and GetResponseStream functions are as below: The CreateWebRequest accepts two parameters from which the second parameter is the HTTP request method i.e. ‘POST’ or ‘GET’. I have used ‘POST’ as this method submits data to be processed by a specified resource. You can set the timeout required during which the External API should be called. Now in my codeunit’s OnRun() function I have written the following code so that the External API URL i.e. Scribe map is hit and the real time integration between NAV and CRM takes place. I am passing five field values from Dynamics NAV. Note: AddToJSon(‘Car_Stage’,CarStageGlobal) where ‘Car_Stage’ is the name of the Scribe field mapping and ‘CarStageGlobal’ is the NAV field value. I have passed the Scribe map URL to UploadJson function and the Json DotNet variable. Conclusion: In this way, an External API can be called from Dynamics NAV. The External API URL i.e. Scribe map URL in this case is hit within seconds and real-time integration is performed quickly. The field values changed in Dynamics NAV are immediately reflected in Dynamics CRM.

Introduction: This blog explains you setup of gift card in Dynamics 365 retail, which can be issue and redeem in store. In POS gift card can be use as payment tender. Just like loyalty Card Casher can check the balance, he can add balance (Money) to the gift card and issue the gift card from POS. Before you setup gift card in Dynamics 365 retail, you should Set up a retail service product to represent gift cards. If cards have bar codes, make sure that the correct bar codes are associated with the gift card product. Let’s begin. Step 1: Open the Dynamics 365. Go to the Retail and Commerce > Headquarter setup > Parameter > retail parameter Click on Posting. Step 2: In the Gift card product field, select the gift card product. This this case “9999” is gift card product No. you can select your gift card no. Gift Card Company: the legal entity that holds the liability for gift cards. In the Journal field, enter the name of the journal to use when intercompany journal entries are created. Journal entries are creating during the statement posting process. In the Serial number templates fields, enter the start date, end date, and gift card numbering template to use when generating electronic gift cards. If the gift card template doesn’t expire, leave the End date field blank. Conclusion: By following above steps you can setup gift card in Dynamics 365 retail.  

In this blog article, I will explain about the new updates of Power BI related to Data bars for new table & matrix (preview). These are the new type conditional formatting to the table and matrix visual called as data bars. Data bars are a quick way to format data and to make it easier to compare. There are two ways two ways to turn on data bars.   1) From the Field itself and   2) From Menu Select Data bars on any numeric measure from your matrix or table. This launches a dialog for customizing the data bars. We can set the properties for data bars like we can set the bar color , min and max value. See below screen captured: Once you confirm with settings, you’ll see the data bars applied to the visual. You can also turn on color scales and data bars from the formatting pane by selecting Conditional formatting. Set Color scales or Data bars to On to apply the default settings or, to customize the settings, select Advanced controls.

Introduction: This blog explains options available for sharing of Schedule Board in D365 Field Services Pre-requisite: Latest Field Service Solution of D365. Procedure: Open Schedule Board, Field Service -> Schedule Board. Open a specific Tab Setting on Schedule Board for e.g. Facility as highlighted below. Click on field “Shared With” dropdown. Schedule Board can be shared with below 3 options Everyone – Schedule Board is shared with all Users. Just Me – Schedule Board is shared with Login User Only. Specific People – Schedule Board is shared with Specific People. Steps to Share Schedule Board with Specific People: Select “Specific People” option in Shared With field of Tab Setting on Schedule Board. Open “Schedule Board Settings” entity records from Advanced Find. Open Schedule Board of Specific People record from the results. Click on “Share” button in ribbon. Add new User by Clicking on “Add User/Team” option and provide privileges as per need. Conclusion: This blog explains the options to share Schedule Board and, also how a Schedule Board can be shared with specific Users only.  

Introduction: Zapier is an Integration tool which allows users to connect various Web Apps.  Zapier is used for simple small scale integration purpose. In this article, we will learn how to create a basic Zap (Integration Process) for Integrating Accounts from Salesforce to Microsoft Dynamics CRM. Pre-requisite: Salesforce Microsoft Dynamics 365 CRM Zapier Steps: Login in to your Zapier. First Step is to create connection for your Source and Target Systems. Click on ‘Connected Accounts’ Tab for creating Source and Target Connections. After selecting the connector, you will be prompted to enter credentials to connect to the systems.List of all the Connected systems/ Apps will be displayed under My Connected Accounts. You can Test, Reconnect or Disconnect the Connections.  Now Click on ‘Make Zap’ to create your new Zap i.e. Integration process definition. Choose the Trigger App. i.e. your Source. Here, we are using Salesforce as our Source. Choose Trigger. i.e. Select an event, based on which you want your Zap to execute. Here, Creation of new Account in Salesforce should execute the Zap; so, we have selected ‘New Account’ Select your Salesforce Connection. You Test your connection by clicking on ‘Fetch & Continue’. If the test is Successful, you can even view the record which is fetched by clicking on ‘view your account’ After setting up the trigger, we have to setup Action. Now, we have to select our target system. Here, we are Microsoft Dynamics CRM as our target. Choose an Action. i.e. Create or Update operation you want to perform on target. Here, we will select ‘Create Account’ since we want to create an Account in CRM which is integrated from Salesforce. Choose your Microsoft Dynamics CRM Connection. Now we have to Map fields of Source fields to Target fields. Click on  target field to get drop for list of source fields. Map all the required fields. After Mapping all the fields, press continue to Save the mappings. Then you can test the Mapping by clicking on ‘Create & Continue’. This step will create the new record in target per the Mapping and data that is fetched from Source in step 7. You can view the record created by clicking on ‘view your account’. You can click on button add more actions or Click on ‘Finish’ button Name your Zap and Turn it on.You are all set for Integration!!

Introduction: In Dynamics 365 Operation retail POS, we have different button on POS of different function. Some time we have a requirement from client he want some specific button on POS. In This blog I am going to show you how to add button on POS Screen. Follow the below steps. Step 1: Open the Dynamics 365 Operation. Step 2: Go to the Retail And Commerce > POS > Screen Layout Step 3: Once you click on it, list of screen layout will open. As per you Store Profile  select  layout. In this case my layout of  A2CP16:9C Step 4: We all Know that In dynamics 365 POS, there is different button grids, As per requirement we will add demo button in Shift and Drawer button. So select the button grids and click on designer button Step 5: Once I click on it. My button designer will Open. Step 6: Right click on the last button and click on Add row. In Row will be added. Right click on button and select Button property. And set the Property Step 7: Click on OK Button and close the designer. Go the Channel Database and Run the Job No. :- 1070. Conclusion: With the help of above steps, you can add, remove or create Customized button designer view for the MPOS and CPOS