In this blog, we shall see how can a user make simple modifications to the CRM Portal Entity Form using ‘Entity Form Metadata’. Pre-Requisites: D365 CRM Portals D365 CRM Environment Why Use Entity Form Metadata? Entity Form Metadata has a modification logic to arguments or has the ability to override the functionality of form fields which isn’t possible using the CRM’s native editing capabilities. Entity Form Metadata allows the user to configure specific pieces on the form like a sub-grid, the notes section or an entire Section or Tab on the form which cannot be modified at the top level configuration. Scenario: In the following scenario the user will see how to make simple customizations like converting a “Lookup” entity field to a “Dropdown” field  on the Create Case Entity Form on CRM Portals using Entity Form Metadata. In the following image below we see that the ‘Product’ field on the  Create Case  Entity Form which is a look up field which we will be converting to a dropdown field using ‘Entity Form Metadata’. Fig 1. Image of the Create Case Form before making changes using Entity Form Metadata Process: In order to make the above changes to the attributes that are present on the Entity Form in CRM Portals the user will have to create a Entity Form Metadata which will convert the lookup attribute to a dropdown list. Step 1: The user will have to go on the CRM Main Menu to Portals> Entity Forms> Customer Service-Create Case Form as shown below. Fig 2. Selecting the Create Case Entity Form Step 2: On the Entity Form the user will have to scroll down to the form till Entity Metadata property doesn’t appear. The user will have to create a new Entity Form Metadata by clicking on the ‘+’ option to the right as shown below. Fig 3. To create a new Entity Form Metadata Step 3: In the New Entity Form Metadata use will have to select ‘Type’ as ‘Attribute’ and select the Entity from the drop down list in ‘Attribute Logical Name’ to which the following change is to be made in this case we will select the ‘Product’ field. Under ‘Control Style’ select the Control Style as ‘Render Lookup as Dropdown’. Fig 4. Entering Specific Details into the Entity Form Metadata Dialogue Box. Step 4: Click on ‘Save and Close’ once the details is entered. Now open the Portal Form Page to which the changes are made. The user will find that the ‘Lookup’ Product field is converted to a ‘Dropdown’ field. Conclusion: Thus, in this way user can make simple customizations to the Entity Form Page in CRM Portals using ‘Entity Form Metadata’ which isn’t possible to be achieved at top level configuration methods.  

Microsoft Dynamics 365 App Development Services is a new generation business application platform from Microsoft that provides an end to end solution to all your growing business needs starting from design, development till the appsource listing and future enhancements. Our App advancement administration group has profound skills in creating sophisticated business applications on the head of Dynamics 365 for our accomplices. We help you through the whole lifecycle, from Development to AppSource posting and improvement support, permitting you to concentrate on your Business Strategy and Marketing. Once the application is prepared and inside tried, we will work with you to present the application to Microsoft, address any issues and get the application recorded on the AppSource. Project Managers often struggle to manage the project plan, keep the Gantt Chart updated.  As there are many activities under the PM’s umbrella to ensure the project delivery goes out smooth and successful. CloudFronts – PM App helps you to keep your project plan updated. Now, you will ask how does that happen? Following is what we do: 1.       We create the Gantt Chart, in which we: List down the Activities Assign duration Assign Billing Code Assign Resources Assign Predecessor’s to the Activities: This is an important activity. What happens when a predecessor is assigned to the task is, that task goes in inactive State. Unless the previous task is marked complete, the dependent task doesn’t turn active. Now, it is Project Manager’s responsibility to ensure that there is 100% time entry done for that task. This will tell you that the task is actually complete. PM-App also provides you this information. Once you double click the task, you see a Progress Field over that. If that is marked as 100%, means the time entry for the task is done by the developer completely. Now the project manager can safely mark the task as complete which is green in colour, so the dependent task becomes Active. Tip: A well-managed Gantt chart provides a lot of benefit to all the stakeholders, so always keep it updated.

Problem Statement: User Syncs data in Field Service Mobile App for first time a large data transfer happens and it takes a long time may be around hours depending on data in D365 Field Service. This blog will explain how to filter data been stored in Mobile and save time for data transfer while syncing. Solution: Below are steps to filter data explained with scenario for displaying only Work Order assigned to Login User. 1. Select “Work Order” Entity and click button “Sync Filter” as highlighted in below screenshot 2. Click “Add Condition” button as shown below 3. Click “Save & Close” button after conditions are developed. 4. Publish Solution. Conclusion: Sync Filter saves data stored in Mobile and time for syncing. We need to create Sync Filter for all business entities.  

In this blog article, I will explain you how to develop and deploy an OLAP Cube. This article is help to learn creation of OLAP Cube in SSAS. An OLAP cube is a technology that stores data in an optimized way to provide a quick response to various types of complex queries by using dimensions and measures. Step 1: Start Analysis Project Click on File -> New -> Project -> Business Intelligence -> Select Analysis Service -> Analysis Services Multidimensional and Data Mining -> specify name for the project -> click Ok. Step 2: Creating Data Source In Solution Explorer, right click on Data Source -> Click on New Data Source -> click Next -> click on New button. For Creating a new connection: 1)  Specify Your SQL Server Name 2)  Select the log on option 3)  Select the database name from the server Then click on Next -> Next -> Assign name for Data Source  -> Finish. Step 3: Creating Data Source View In the Solution Explorer, Right Click on Data Source View -> Click on New Data Source View -> Select Relational Data Source which we have created in Step 2. -> Click on Next. First move your Fact Table to the right side to include in object list. Select Fact Table in Right Pane (Fact product Sales) -> Click On Add Related Tables Then click on Next -> Finish Data Source View is ready. Step 4: Creating New Cube In Solution Explorer -> Right Click on Cube-> Click New Cube -> Click on Next -> click on Use existing tables -> Next. Select Fact Table Name from Measure Group Tables -> Click Next. Choose Measures from the List which you want to place in your Cube -> Click Next Then click Next -> Next -> Assign Cube name -> Finish. Your Cube is ready and you can see the newly created Cube and dimensions added in solution explorer. Step 5: Deploy the Cube In Solution Explorer, right click on Project Name -> Click Properties. Specify the target Server name and server mode. In Solution Explorer, right click on Project Name -> Click Deploy Once Deployment will finish, you can see the message Deployment Completed in deployment Properties.  

Dynamics 365 for finance and operations is an ERP system built and designed to match your business needs in this modern day business scenario. Elements are currently as much a business system as it is innovation deliverable, some portion of a bigger biological system where data pulled from unique channels, (for example, social, IoT, and Office) is caught, investigated, and spread so as to help explicit business objectives. Make planning simpler by giving your spending chiefs simple to-utilize apparatuses. A wizard causes them to make spending plan worksheet formats for Microsoft Excel.  This cloud-based ERP framework gives the pertinent data you have to convey vital, information-driven bits of knowledge to key divisions. Additional quick monetary bits of knowledge drive corporate procedure and development, declining obligation through effective assortment of the board. Introduction: Blow blog, describe you about how to create,  modify Receipts, invoice, Order summery report and rest of other document for MPOS and CPOS. You can create multiple receipts with different layout for single entity. Let begin with this Exercise. Step 1:- Go to the Retail and commerce > Channel setup > POS setup > POS > Receipt formats. Step 2 :- Select Receipt format 1 and click on design button. Once you click on Design button browser will ask to Open  Microsoft.Dynamics.Retail.RetailDesigner Host.application Click on Open Button. And sign in Dynamics Workflow Editor. Step 3:- Designer window is look like below screen shot. Step 4 :- In Designer window you can able to see Form Information. Form ID :- ID of receipts  , Form Name :- Name of Form , Form Description :- Description of From. Step 5:- On Left Side, you can able to view Header, Line, Footer. In Header you can click on drag  listed element in design work space. For E.g. Store ID, Staff Name, Receipts No. Transaction ID.  Header element will print on top of the receipts and will print only at once. Step 6:- In Lines, you can click on drag  listed element in design work space. For E.g. Product ID, Description, Unit Price, quantity.  Line element will print on middle  of the receipts. Step 7:- In footer, you can click on drag  listed element in design work space. For E.g. Total, TAX Amount, Tender Name .  Footer element will print on bottom  of the receipts. Step 8:- Object Information is used to set property of Element of Header, Lines and footer which is Align – Set the alignment of the field to either Left or Right. Fill char – Specify the white space character. By default, an empty space is used, but you can enter any character. Prefix – Enter the value that appears at the beginning of the field. This setting applies only to the Lines section of the layout. Characters – Specify the maximum number of characters that the field can contain if the element contains a variable. If the text in the field is longer than the number of character that you specify, the text is truncated to fit the field. Variable – This check box is selected automatically if the element contains a variable and can’t be customized. Font type – Set the font style to either Normal or Bold. Bold letters use two times as much space as normal letters. Therefore, some characters might be truncated. Delete – Click this button to remove the selected part from the form layout. Step 9:- Click on Save button. You receipt Layout will be save. Conclusion: Follow this steps to Create or modify receipts layout which is used in CPOS and MPOS.

In this blog, we shall see how can a user uninstall the ADX Portals from Microsoft Dynamics CRM Online and what are the various that a user might face while uninstalling the Adxstudio solutions from CRM before installing the new CRM Portals. Pre-Requisites: D365 CRM Portals D365 CRM Environment How to Uninstall the ADX Portals: According to ADX Studio the following is the procedure to uninstall ADX Portals from the CRM Environment: “The process of uninstalling the solutions is to delete the solutions in the reverse order they were installed. If customizations have been made that depend on any of the components in Adxstudio solutions, those customizations must be undone before a delete will be successful. Delete any suplementary Adxstudio solutions such as Adxstudio Forums, Adxstudio Ideas, etc. that may have been installed. Then delete Adxstudio Portals solution, then delete Adxstudio Portals Dependencies solution.” Process: Step 1: The user will have to go Settings in the ‘All Select Area’ and click on Solutions option. Step 2: The user will have to make a list of the Adxstudio solution that are present in the CRM Solution list. *Note: The solutions are already arranged in the grid view in descending order of their installation. The user must uninstall in that order only (with Adxstudio installer to be the last solution to be installed). The following below is the list of solution in the descending order of their uninstallation. *Note: The following list may/may not contain all the solution components of Adxstudio but consists of most of the solutions that are used in ADX Portals. Sr. No. Solution Name Display Name 1. AdxstudioIssuesWorkflows Adxstudio Issues Workflows 2. AdxstudioIssues Adxstudio Issues 3. AdxstudioIdeasWorkflows Adxstudio Ideas Workflows 4. AdxstudioIdeas Adxstudio Ideas 6. AdxstudioBadges AdxstudioBadges 7. AdxstudioCareersWorkflows Adxstudio Careers Workflows 8. AdxstudioCareers Adxstudio Careers 9. AdxstudioBlogs Adxstudio Blogs 10. AdxstudioIdentityWorkflows Adxstudio Identity Workflows 11. AdxstudioPortalsWorkflows Adxstudio Portals Base Work 12. CustomerServiceSurvey Customer Service Survey 13. AdxstudioHelpDeskWorkflows Adxstudio Help Desk Workflows 14. AdxstudioHelpDesk Adxstudio Help Desk 15. AdxstudioCommerce Adxstudio Commerce 16. AdxstudioForumWorkflows Adxstudio Forum Workflows 17. AdxstudioForums Adxstudio Forums 18. AdxstudioEventManagement Adxstudio Event Management 19. AdxstudioWebForms Adxstudio Web Forms 20. AdxstudioIdentity Adxstudio Identity 21. AdxstudioPortals Adxstudio Portals Base 22. AdxstudioPortalsDependencies Adxstudio Portals Dependencies 23. AdxstudioCRM2011ProductivityPack Adxstudio CRM 2011 Productivity Pack 24. AdxstudioInstaller Adxstudio Installer Step 3: Once all the solutions of ADX Portal are deleted or uninstalled from CRM Environment the user can then configure a new portal for the same CRM Environment. Problems Faced while Uninstalling/ Deleting solutions of ADX Portal The user might face many difficulties while uninstalling / deleting solutions from the CRM environment. One of the major problems which users mostly face is “Solution having other internal Dependencies” which prevents the solution from being uninstalled. In the below example we will try to uninstall the “Adxstudio Portal Base” solution from the CRM Online environment. Step 1: Select the ADX Portal solution that you want to delete from the system, in this case it is “Adxstudio Portal Base” solution. Step 2: On clicking the delete command the following dialog box will appear click on OK to proceed. Mostly the following error message appears as shown below(i.e. the error message pops up cause the solution that the user is trying to delete has internal dependencies), the user will have to click on ‘Details’ to view the list of dependencies. Fig 3.1 Pop up dialog to Uninstall the solution. Fig 3.2 Error message that solution cannot be deleted Fig 3.3 List of Dependency Details which are preventing the solution from being uninstalled. Step 3: The user has now the list of dependencies due to which the solution cannot be uninstalled from the CRM Environment. The user has to remove/delete the dependencies in order to uninstall the solution. If the user is able to remove the dependencies the user can proceed to uninstall the solutions. Issue Faced: Most of the times the dependencies cannot be deleted which in return causes the solution from being uninstalled from which in return causes the ADX Portal from not being uninstalled. The following are possible ways of dealing with the issue faced: Mostly the users will have to leave the solutions that aren’t being uninstalled as residual solutions and try provisioning the new CRM Portal. Else will have to wait for Microsoft to fix the following issue of not being able to uninstall the residual solution in their future updates on Portals. Conclusion: Dependencies in the Adxstudio solutions can cause the ADX Portal solution from not being uninstalled. In this case the user can try installing the CRM Portal leaving the uninstalled solutions as ‘Residual solution’. Waiting for the following issue to be fixed in further updates on portals from Microsoft.

Recently while connecting to Dynamics 365 Operations STAGE environment through TIBCO Cloud Integration, we got authentication error of AADSTS65001. In this article, we will discuss how to resolve this authentication issue. Error details: Connection test failed: Verify that the associated connection information is valid and that you have access to this OData service. The following exception message was returned from the OData service: AADSTS65001: The user or administrator has not consented to use the application with ID ‘********-****-****-****-************’. Send an interactive authorization request for this user and resource. Trace ID: af595cf2-0b8c-4cd7-ae28-c56e18031300 Correlation ID: e1d5cece-89d1-4fda-a954-39f740c0cb4f Timestamp: 2017-04-05 08:38:45Z Solution: In Azure Active Directory, for connecting to Dynamics 365 Operations through SCRIBE we create a Native Application and use its Application ID and Redirect URI as Client Id and Authentication URL respectively in SCRIBE. TIBCO Cloud Integration Microsoft Dynamics 365 Operations Connector: AZURE Application Registration: In an Azure Active Directory, we had two Application (one Native and one Web app/API) pointing to same Dynamics 365 Operations STAGE environment; which was creating an authentication conflict. So, we changed the App ID URI in Web app/API Application. In our case, we appended /1234 in the App ID URI. After the modification, the authentication was successful. We were able to connect Dynamics 365 Operations STAGE through Scribe using the Native App’s Application ID and Reply URI.

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.