Introduction: Have you ever wondered what happens to the user owned records in CRM when the user itself is deleted from CRM? Will the records get deleted? Or Will it be assigned to some other user? What will happen to the existing system jobs? Let us see in the below example. Description: Suppose there is a user named “Somesh Siripuram” and this user has its own account records. The owner of this records is “Somesh Siripuram”. Now the user is being deleted from the admin portal and no longer has access to Office 365 and CRM. Login with system administrator and check for the deleted user. The user will be listed in “Disabled User” view. When you open the user the email address and the user name of the user will be changed and some number appears Now, it’s time to check the deleted user owned records Thus, we can see that records neither gets deleted nor the owner of the records get changed. Manual assigning of records to another user is required. Other effects: Waiting jobs will remain as waiting until it is cancelled. New system jobs (where workflow owner equals to disabled user) will fail. You need to change the owner manually, they are not auto assigned to system  

Package configurations is very important to achieve flexibility SSIS package, easy configurations allow used to changes and reuse the solutions in different environment with them customize settings and rules. SSIS package supports different types of configurations, these package configurations is also depended on deployment model. In this blog we will discuss about the Project Parameter configuration using the Project Deployment model. Let’s make the SSIS package Solution to Project Deployment model. Right Click on the SSISProject Solution Name, Click Project Deployment Model. Follow the Wizard: Click Next: This will provide you list of packages that you need to convert, then click next. Next will be setting up the protection Layer for the Package: Then Click on Next and then it will convert your Solution to Project Deployment model. Project Deployment Model allows you to configure the package at project level, it groups the Package configurations together that allows user to easily configure Parameter.

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.

Physical negative inventory functionality is mainly used for issuing the stock for insufficient inventory. If Physical inventory checkbox is selected then system will allow to issue an item though stock is not available into inventory. Path: Inventory Management > Setup > Inventory > Item Model Group Below is example how to issues stock if there is insufficient inventory. You can see the below item for which On Hand inventory is not available though I want sale these stock. Create the sales order and enter item, quantity, Unit cost and confirm the sales order. Post the Packing slip to sell or issue the stock. Check the On hand inventory after posting Packing slip. You can check On Hand Quantity is showing negative. Conclusion: These functionality helps to issue stock through sales order, Production order, adjustment journal though stock is not available or insufficient.  

Partially built using the Notifications in the UI the smart notifications gives you advice when you use the application. As an example; if you create a new sales invoice for a customer that have an overdue balance you will see the below notification. Another example is when you close a sales order you receive a message saying that the order has not been posted (I am a bit skeptical to this one since in my world posting a sales order is not done by the same person that’s entering it). Luckily this is configurable and each user can turn the features off and on through the My Notifications setup where conditions also can be applied. I think this is a cool concept and I see a potential to create custom notifications to support how the business wants to operate and to reduce common user mistakes.

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

In AX 2012, we had an option Personalize to view the form and form control layout; Form, DataSource and field details; Add and manage form design. In this blog article, we will see how we can find form and form control details in Dynamics 365 for Operations. In this blog we will view the Customer Name – form control details. 1. Go to Accounts Receivable -> All customers -> Right click on the ‘Name’ field. 2. Select Form Information -> Form Name 3. In Form Information go to Administration Fast Tab. You can find all details regarding form control – Customer name.

Problem Statement: In CRM, most organizations generally import products from other Source through Excel or other data import means. In general, we do not want to publish the product as soon as they are created because we need to set the price list and units before they are available anywhere in CRM. If there are many products, CRM does not allow to publish all the products at once. It becomes very painful to publish each and every product. This is unimaginable if the count is in thousands and more. See screenshot below which suggests I cannot see the Publish option if I select more than 2 products in the view: Solution: The best way to tackle this is: Create a Default Product Family (Dummy product family). Add all the products in the Dummy product Family. You can do this while importing products as well by setting the parent product as the Default Product Family. In case you already have a family and hierarchy, you can still follow this approach by setting the parent of root family as the Default Product Family. E.g. If you have products as the following defined hierarchy: Product Family A A1 A2  A3 A31 A32 Product Family B B1 B2 … In this case, you can set the parent of “Product Family A” as Default Product Family Once this is done, you can now import all the products, set up pricing and units as required. This is how your Hierarchy will look like in CRM: When all the products are ready, go to the Default Product Family A On the ribbon, Select Publish –> Publish Hierarchy This will publish all the products in the hierarchy. Since all your products are in the hierarchy of the “Default Product Family”, all the products will be published saving A LOT of Time. TAKE THAT CRM … You CANNOT SLOW US DOWN!!