These fields which are everywhere but you don’t really pay attention to really mean something worth. So if you feel you want to get hold of someone for modifying a record. Maybe also take a look at Modified By (Delegate) just in case so that the actual user might be someone else who wanted to do another thing on that record. 🙂 Impersonation is one of the basic aspects of a plugin step that you need to carefully design to let another user (usually Admins for most implementations) make the plugin run under their context instead of giving more security roles/privileges to every other new user. Well, the same goes for Created By & Created By (Delegate) also! Modified By Usually, when you update something on a record, the Modified By is updated as expected. But notice that Modified By (Delegate) is not updated. That’s because you are the rightful owner of the record and there’s no other person involved. But what is someone else is modifying the record (who don’t have access to that record)? In that case, the Modified On (Delegate) field is populated with the name of that user. In such scenarios, Modified By (Delegate) the user is the one who caused changes to the record. Why Modified By (Delegate) was populated The reason this was populated was that the record was updated through a plugin by a user who doesn’t have write access to the record. But because the user invoked a plugin which was Impersonating as a User who has rights to the records, the record was successfully updated. And this, the actual user who called the plugin is the one who will be populated in the Modified By (Delegate) field. Hope this quick tip helps!

Inventory Posting Group: Use to specify the type of Inventory or group the item. Inventory Posting setup: Use to combine Inventory Posting group with location codes. Each combination is then mapped to the inventory accounts, WIP account, and other variance accounts relating to inventory in the chart of accounts. Steps: Set up Inventory Posting Group In the search option, enter the Inventory Posting Group and then choose the related link. Select New. In the Code field, type a unique identifier. In the Description field, type description of Inventory Posting Group.   Steps: Set up Inventory Posting Setup In the search option, enter Inventory Posting Setup and then choose the related link. Select New to insert a new line. In Location Code Field, select the relevant location to combine with the inventory posting group. Select the relevant inventory posting group in the Inventory Posting Group Code field. In each relevant account field, enter the G/L accounts that will be used to post transactions to: Inventory Account: Specifies the number of the G/L account that item transactions with this combination of Location and Inventory Posting group posted to. Inventory Account (Interim): Specifies the number of the G/L account to which to post the transactions with the expected cost for items in this combination. WIP Account: Specifies the general ledger account number to which to post transactions for items in WIP inventory in this combination. Material Variance Account: Specifies the number of general ledger account to which Material variance transactions for items in this combination. Capacity Variance Account: Specifies the number of general ledger account to which to post capacity variance transactions for items in this combination. Subcontracted Variance Account: Specifies the number of general ledger account to which to post subcontracted variance transactions for items in this combination. Overhead Variance Account: Specifies the number of general ledger account to which to post capacity overhead variance transactions for items in this combination. Overhead Variance Account: Specifies the number of general ledger account to which to post Manufacturing overhead variance transactions for items in this combination.   Steps: Assign Inventory Posting group to Item In the search option, enter Items and then choose the related link. Open the Item card Expand the Cost & Posting FastTab, in the Inventory Posting Group field, enter the appropriate posting group. Conclusion: Inventory posting group and setup use to posts entry to the G/L account specified for the combination of inventory posting group and location code linked to the item line entry.

Customer service is the most important element in today’s business. If you do not take care of your customers well, they will not stay loyal to your brand or products. Hence, you need to do everything possible to provide them with the best service. Unfortunately, these days a lot of companies are struggling with this thing. Dynamics 365 for Customer Service from Microsoft is the best product as it will help you as a business to focus on the right aspect of the business. It will not only streamline the processes in your company but it will help you to become efficient in addressing issues that are of grave concern to the customers. Installing and using this product is easy. Since there are certain things that are confusing. Here is a blog explaining how to tackle a problem you will face. Problem: Whenever we are assigning the new owner to Lead present in the CRM, the Last Date Modified of the Email Activity gets changed to the current date and time when the new Owner is assigned. Now due to this, all the Old Email Activity with other owner get re-posted to the Activity Timeline of the Lead because email activity by default sort by the Last Date Modified. Now, above the situation is happened due to the 1: N relationship present in the CRM between Leads and Email Entity which has “Parental” Type of Behavior. So, when we assign a new owner then some of the fields get modified. Following is a step where you can find Lead to Email Relationship: Go to Solution and find the Lead Entity Click on Lead Entity and then open 1: N Relationship 3. Now open Lead Email Relationship, it will be same as the following:  Now to Change the Current Behavior of the Relationship So, Email Activity should not be re-posted whenever the new owner is assigned to Lead. Step to change the Relationship Behavior: 1. Change the Type of Behavior to Configurable Cascading under the section of Relation Behavior After changing the behavior, change the Cascade All to Cascade none in Assign field. This will not change the owner of the Email Activity as well as the Last Date Modified of Lead’s old Email Activity when Lead is assigned to new Owner. Following is before and after of the configuration has been changed. If we don’t change Relationship behavior, the following is the scenario 1.1 Lead Email Relationship Configuration 1.2 Before assigning the owner 1.3 After assigning a new Owner If we change Relationship behavior, Parental to Configurable Cascading and Assign (Cascading All) to Assign (Cascading None) 1.1 Lead Email Relationship Configuration 1.2 Before assigning the owner  1.3 After assigning an Owner Hope this helps!

While Creating Any Cloud-Hosted Environment in LCS it Is Necessary to create Azure Connector for which ARM(Azure Resource Manager) configuration is necessary. So this article will help you to create Azure Connector. Steps to follow :- Role assignment at the azure portal For Proper Working of Azure Connector make sure you have mentioned role assignment in your azure portal.Visit the Azure portal with the same credential as that of LCS and visit subscription section. Now select Access Control(IIM) In which click on Add Button and select Add Role Assignment. Now Configure the Add Role Assignment field as follows and save those configurations. Authorize link Now Navigate back to LCS in which Project Settings>>Azure Connectors and make sure to autorize link by clicking authorize button. Create Add option for connector Click on Add Button in Azure Connectors section and add Name, Azure subscription Id ,  and Toggle Configure to Azure Resource Manager(ARM) option to Yes. Click on next and Check for the following page Again Click on next move to the next step Upload Management Certificate Download the management certificate Now Upload Downloaded Certificate in Azure portal as follows And upload the certificate Select Region for Connector Navigate back to previous LCS session and Complete setup By selecting required Azure Region Click on confirm and your Azure connector is created and the screen looks as follows  

Customer service, sales, marketing, finance, and operations are the five main pillars of any organization. When you take care of these aspects well, you can easily beat the competition that is out there. Unfortunately, not many companies focus on these elements as they do not know what exactly they need to do to streamline the processes. Dynamics 365 for Finance and Operations is the solution or answer that you are looking for to scale up your business.  This product will help you to stay on top of your toes in addressing issues in finance and operations with ease. Your staff is going to become a lot more efficient when they use this product. Installing and using this software is pretty easy.  Here is how you do data fidelity checker: In this blog, I am going to shed some light on a new feature that is already available in the public preview of Microsoft Dynamics 365 Retail. General availability will be sometime in Oct 2019 The statement posting process is used to account for the transactions that occur in Cloud point of sale (POS) or Modern POS (MPOS). This process uses the distribution schedule to pull a set of POS transactions into the headquarters (HQ) The parameters that are defined on the Retail parameters and Stores pages are used to select the transactions that are pulled into individual statements. A retail transaction consistency checker(Validation checker) identifies and isolates inconsistent transactions before they are picked up by the statement posting process. We faced a lot of issues with statement posting. The process often asks you to run a validate store transaction job but still, the statement won’t post. Raising an MS support ticket is the only way to fix this. I believe data fidelity should make the statement posting process more efficient. Fidelity checker does the following: Data fidelity checker will check the data for omissions and anomalies and only those transactions that pass the validation will be included in the statement process. Validate records, gift cards, tax table Fix the transactions by users who are not in line with the auditing purpose.  Also, currently, the statement posting process first reserves the inventory throughout the day as the transactions are carried out. Which is temporary. Then at the end of the day during the statement posting system removes these reservations for inventory created and then creates sales orders, payment journals, and ledger journals in the system. This process is not very efficient because when all the transactions are processed together at the end of the day, it could result in overloading and failure. To address this in future this process will be removed all together. Which means no temporary inventory job will be created. A new job that will run as per predefined schedule will create sales orders, invoice them, and create, post, and apply for payments. The statement document that gets created at the end of the day will only be used to calculate and post any counting variances.

1. Saving and personalizing list views. Suppose we want to switch between pages and we want to add filters, so to achieve this we have to add filters every time we come back to that page, this feature was not available in the previous version of Business Central but now it has been added by the developers. We can save a combination of filters as our view and access it again and again.   2. Personalize actions and navigation on your Home page With the Business Central Wave 2 Release users can easily add their desired pages to their Role centers, making these pages easily accessible to the user. 3. Design for Extensibility. Users can adjust actions and action groups on their Role Center. Adjust the navigation menu items and grouping on a Role Center. Customize user profiles by designing page changes that will apply only to a specific profile in your extension.

Customers are looking for experiences when they go for shopping these days. They are not planning to use a particular store if they do not get the best experience. In contrast, if a store is providing the best service, customers are very much interested in visiting that store again. If you want to be a successful retailer, you should plan on using Microsoft Dynamics 365 for Retail Management Solution.  When you use this particular product or software, you are not only going to streamline the process but will provide the best customer experience to your customers apart from improving the retail management. You are going to easily scale up your business high when you use this particular software. Activating/installing POS on a new system is a straight forward process. However what I have noticed on several occasions is that connecting the printer with hardware stations can sometimes take too many efforts than the standard defined process. The standard process should ideally work and should not take too much effort to get the POS to work. However in some cases when the standard process does not work, you need to find a workaround to get the things to work. Here in this article I am going to suggest several ways to get your POS to connect with printer if there are printer/peripherals connectivity issues Reinstall latest Monroe CCO OPOS driver and hardware station Make sure to test the connection. The ping should be successful after installing the hardware station Check printer name in printer settings of your system and also in POS hardware profile in F & O Make sure in OPOS ADK App has printer added to it. If not then right click on POS Printer>Add new device>Select printer>Add New LDN(Printer Model name as defined in the printer settings)   If still there are issues, you can try the below steps  Make RetailHwsUser part of the local administrator group To do that first: Open computer manager by right clicking windows start icon 2. Double click on Administrator group 3. And Add the RetailHwsUser 4. Go to users tab  and assign password to this new user profile(RetailHwsUser) 5.  Login as RetailHwsUser and setup the LDN to the printer/device name 6. Now reinstall the hardware station and restart the computer. After restart if it still does not work, Please reinstall the hardware station once more Now you should be able to pair and print the receipts. Most of the time, this works, however,if these steps still don’t work then please raise it to Microsoft support team.

Part 1/4: Using FOR EACH Loop with KingswaySoft Connector for CRM Invoice Integration. Introduction: The SSIS ForEach Loop container will repeat the control flow task for N number of times, which is similar to Foreach loop in any programming language. This concept can be used for Integration of Header and Lines concept like Invoice. Our Scenario: For demonstration purpose, we will consider an Invoice Integration Map for Integration of Invoice and Invoice Details from SQL to Dynamics CRM. In this blog, we will use for Each Loop to Loop over all Invoices present in SQL Server DB and their respective Invoice Details. The Map for Invoice Integration after Completion will look like following after completion. Integrating Invoice Step 1: Create an execute SQL task which will count the Number of Invoices present in SQL Server DB having Ported Status marked as Zero. Create variable CNT having Data Type INT32 with initial value 0 to store the count of Invoices. Configure the following settings for the Control Flow Task. Step 2: Add a Sequence Container and double click on the green arrow to apply a condition as follows to proceed only if there are any Invoices are present in the DB else skip the Sequence Container. Step 3: Add an Execute SQL Task to store the all InvoiceNumbers in object variable. Create variable InvoiceNumbers having Data Type Object to store the InvoiceNumbers. Configure the following settings for the Control Flow Task. Step 4: Add a ForEach Loop Control Flow Task and configure it as follows to Loop over Invoices for Integration purpose. In the Collection Section select Foreach ADO Enumerator for Enumerator type and Rows in the first table as the Enumerator Mode. Create variable InvoiceNumber having Data Type String to store the InvoiceNumber for a single record to be fetched in one cycle. Configure the following settings for the Control Flow Task. Step 5: Add a DFT to Integrate Invoice Header. Note: This is the first part of the 4 part blog series. Here are others: Part 2/4: SSIS Integration Map for Invoice Header from SQL Server to Microsoft CRM Part 3/4: SSIS Integration Map for Invoice Details from SQL Server to Microsoft CRM. Part 4/4: Delete Logic for Invoice in case of Incomplete Integration of Invoice details Logic.              

Phase 2/4: SSIS Integration Map for Invoice Header from SQL Server to Microsoft CRM: The Map after Completion will look as follows. Step 1: Add an OLEDB Source and configure it as follows: Click on Parameters and configure it as follows: Step 2: Add a derived column transformation to specify the Customer Type i.e 2 which indicates that Customer type is an Account. Also, we will map the Invoice Number to name, so we will create a copy of it. There is a single PriceList for all Invoices in my case so I have hardcoding for Lookup Purpose. Step 3: Add a CRM destination Block and configure it as follows: We will use Upsert Criteria specified on Invoice Number for Integration. The fields mapped are as following. Step 4: Add the remaining blocks for Custom Error Handling as explained in the Blog in Link: https://www.cloudfronts.com/creating-custom-error-log-table-in-ssis-for-oledb-block-and-kingwaysoft-dynamics-crm-block/ Note: This is the second part of the 4 part blog series. Part 1/4: Using FOR EACH Loop with KingswaySoft Connector for CRM Invoice Integration. Part 2/4: SSIS Integration Map for Invoice Header from SQL Server to Microsoft CRM. Part 3/4: SSIS Integration Map for Invoice Details from SQL Server to Microsoft CRM. Part 4/4: Delete Logic for Invoice in case of Incomplete Integration of Invoice details Logic.  

Part 3/4 SSIS Integration Map for Invoice Details from SQL Server to Microsoft CRM Step 1: Add a DFT to Integrate the Invoice Details in the Control Flow. The Map after Completion looks as follows: Step 2: Add an OLEDB Source and configure it as following: In our case we are Inner Joining Invoice and Invoice details Table based on OrderNumber and  Invoice Details and Products Table based on ProductID. This will help us to retrieve the columns which are not provided in a single Table and are required for Integration of Invoice Details. (Note: this might vary according to your scenario) Click on Parameters and configure it as follows: Step 3: Add a derived column transformation to create a unique name for Invoice Details as an upsert criteria. Step 4: Add a CRM destination Block and configure it as follows: We will use Upsert Criteria specified on Invoice Detail Unique Name for Integration of Invoice Details. The fields mapped are as following. Step 5: Add an OLE DB command transformation to update the Ported status to 1 indicating the Invoice details have been integrated. Configure it as follows: Step 6: Add the remaining blocks for Custom Error Handling as explained in the Blog in Link: https://www.cloudfronts.com/creating-custom-error-log-table-in-ssis-for-oledb-block-and-kingwaysoft-dynamics-crm-block/ Note: This is the third part of the 4 part blog series. Part 1/4: Using FOR EACH Loop with KingswaySoft Connector for CRM Invoice Integration. Part 2/4: SSIS Integration Map for Invoice Header from SQL Server to Microsoft CRM Part 3/4: SSIS Integration Map for Invoice Details from SQL Server to Microsoft CRM Part 4/4: Delete Logic for Invoice in case of Incomplete Integration of Invoice details Logic: