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:

Part 4/4 Delete Logic for Invoice in case of Incomplete Integration of Invoice details Logic Introduction: To handle the scenario where the Invoice Details fail to get Integrated or Incomplete Integration of Invoice Lines the Invoice itself should get deleted from CRM as we don’t want to Integrate Incomplete records. Step 1: Add a DFT to Delete Invoice in the Control Flow as follows: The Map after Completion looks like the following: Step 2: 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. Add an OLEDB Source block with the required query and configure it as follows: Click on Parameters to add a Parameter as follows: Step 3: We have a Ported field in our Data Base which set to 1 once Integrated with CRM. Add a Conditional Split Block to Split into two categories based on the sum of ported and count of ported as follows: Count of Ported = Sum of Ported This indicates that all the Invoice Header and all its Details have been Integrated Properly. In this case, we will add an OLE DB Command Block to update the status of Invoice Header to 1 as follows: Count of Ported != Sum of Ported This indicates that all the Invoice Header and all its Details have not been Integrated Properly. In this case, we will add an OLE DB Command Block to update the status of Invoice Header to 0 just as above where we update it to 1: Once the Status has been Updated we have to Delete the Faulty Invoice Record from CRM. We have performed Lookup based on Invoice Number as follows: Output: Source (SQL Server) Invoice Header- Invoice Details- Execution of Package – Destination (CRM) We can see that one Invoice is Integrated which had all proper data. The Other Invoice which failed to Integrate in some aspects has been automatically deleted from CRM. Note: This is the fourth 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

We are quickly transitioning over from Organization Insights which came as a managed solution inside D365 to CDS For Apps Analytics on the PowerPlatform Admin Center. And now, the same is revamped as Capacity in PowerPlatform Admin Center. So, if you go to Storage in CDS For Apps analytics, you’ll see this – Capacity You can access Capacity section directory from this URL – https://admin.powerplatform.microsoft.com/analytics/capacity Or from the left hand menu as below – Now, as opposed to previously summarized % of the total capacity available, Microsoft is providing new entitlements for different types of storage consumption – Zoomed below As mentioned above, the bifurcation is as follows – DATABASE: All other entities apart from the ones mentioned below. FILE: Attachment, AnnotationBase tables LOG: AuditBase, PluginTraceLogBase tables Environment View A Per Environment View looks like below and you can click on the Graph icon to go into the details At this point, information for the Graphical details are yet to be available. I’ll update post this is available for me too. Availability New Capacity model differs and will be available once the current term ends. More information from the links in the More Information section below More Information You can refer more on Capacity here – https://docs.microsoft.com/en-us/power-platform/admin/capacity-storage Hope this quick summary helps!

Maintaining a retail store is not an easy task. You have to take care of several aspects. Unfortunately, not many retailers know how to do it. They struggle to take care of things such as retail store management, providing customer experience and support etc. It is wise to get Microsoft Dynamics 365 for Retail Management Solution if you desire to better the process.  Now, this another product from Microsoft that is aiming at improving the overall performance of your company. Installing and using this software is pretty ease. You might struggle a bit during the initial stages. For example, you might not know things such as POS receipts printing as well as struggle dealing with connectivity issues in Microsoft 365. Here’s everything you need to know how to handle these things. Dynamics 365 for Retail provides mid-market and large retailers with a complete head office and point of sale (POS) solution that includes support for online and brick-and-mortar stores. It can help retailers increase financial returns, improve service, manage growth, reach customers, and streamline efficiencies. Dynamics 365 for Retail supports two types of POS experience: Cloud POS is a browser-based POS that can  be started in any standard browser on Desktops, Laptops, mobile devices. Retail Modern POS (MPOS App) can be used on clients such as PCs and tablets to process sales transactions, customer orders, and daily operations, and to perform inventory management.There are many obvious reasons as to why a retailer would prefer to choose Cloud POS instead of Modern POS: Since CPOS runs in a browser, the application isn’t installed on the device. Instead, the browser accesses the application code from the CPOS server.  Which is why you wont be able to use cloud POS in offline state but these days Internet connectivity is available almost 24/7 so it’s not an issue. A zero-footprint, cloud-hosted solution brings benefits in terms of cost and simplicity. Sales staff can process sales transactions and customer orders, perform clienteling activities, and perform daily operations and inventory management on mobile devices anywhere in the store, and also at PC-based registers. Deployment is easy as no installation is required except for the hardware station which on the main host system. All you need to do is activate the POS. When you change/upgrade your system, all you need to do is re-activate CPOS. You can also set up Hybrid Android app which lets you use CPOS though Android App on any Android phone. One of the advantages of having CPOS is it’s cross platform availability. It can run on any operating system. All it requires is a browser to run.