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.

1. Lock-free number series (Allow gaps in Number Series). Users can choose to mark number series to allow gaps in the series. These number series will be non-blocking, which will boost performance. Add notes and links to data Users can quickly add a note to the data they are currently viewing on the Business Central, these notes can be used if a user needs to add some note to the specific page. 3. Customize a user profile without writing code. (New fields have been added, Caption, Description, Use as Default Profile, Promoted). Users need not have to write code to change a user profile, instead, they can make changes to a user profile from Profile only.

Two departments that are most important in a business is finance and operations. Unless they are efficient and perform well, you as a company are going to struggle a lot. Hence, you need to plan on using Dynamics 365 for Finance and Operations to streamline your business. It is yet another product from Microsoft that will allow your business to tackle difficult issues with ease.  If your staff spends a few hours learning how to use the product they will become quite efficient. They will become super efficient in tackling any hurdles that might come on the way. For example, deleting model/package might not be an easy task. Here are details of how you can do it with ease Many of the time when You don’t want Existing Data Types(Base Enums, EDTs) or Data Models(Table, Views etc)  and many more elements which can ultimately cause naming conflict while development. So Option is either you want to delete those data type or Model consisting those Data Model/Data Types. Following methods are needed to be performed while Deleting model: 1.First Open Services and Select  Microsoft Dynamics 365 Unified Operations: Batch Management Service and Stop that services 2.Navigate To following path K:\AosService\PackagesLocalDirectory And Select Your Respective package/Model and delete that Note:- Here I’m using One box machine so my “AosService” is located at K drive. For other machine users “AosService” can be located at other location so you will look for it and Follow steps same as above. 3. Don’t forget To start Microsoft Dynamics 365 Unified Operations: Batch Management Service again. 4. Now refresh models from Visual Studio as follows You have successfully Deleted the Respective model/Package. Hope this helps!

Hello guys, The two types of point of sale or POS in Microsoft Dynamics 365 for Retail Management Solution are MPOS and CPOS. MPOS is Modern Point of Sale and CPOS is Cloud Point of Sale. There is no offline functionality when it comes to Cloud POS. It has a unique design that allows you to pair it up with the hardware station. The MPOS, on the other hand, is a POS app that one can access with ease on tablets, and PCs. Migrating from MPOS to CPOS is a good option because Cloud POS can run on any platform since the browser accesses the application code from the CPOS server but it can become a time-consuming task if you do not follow the standard process. In this article, I am going to demonstrate how to change/migrate from Modern POS to Cloud POS in Dynamics 365 for Retail. Once you activate Cloud POS you can access POS directly from any web browser. However, you do need to install the Hardware station. Because CPOS runs in a browser, the application isn’t installed on the device. Therefore, CPOS can’t directly access POS hardware or work in an offline state. Step 1: Go to all Retail stores Step 2: Click on the Register for which you want to change from MPOS to CPOS Step 3: Click on the device Step 4: In the application type Select Retail Cloud POS Step 5: Change Activation status to Pending and click on Validate devices for activation. Click Ok for all workers Step 6: Click on Cloud POS URL Step 7: Activate it using HQ user ID and password. Select appropriate store and register that you had activated on HQ which is in pending state. If it’s in activated state then it wont reactivate. Step 8: Next step is to install the Hardware station so you can connect hardware peripherals to your POS. Go to your store and scroll down to Hardware stations. Select shared. In the Hostname field enter the name of your computer(find it in system information of your system) and click on download. Step 9: Run the downloaded file. It may ask you to install OPOS Common control driver from the link. Download the latest one and click next. Step 10: Enter the Retail server URL Step 11: Open IIS then go to SSL certificate Step 12: Double click on Server certificate and click on Create self signed certificate Step 13: Select the SSL certificate Step 14: Use any of the open ports or you can use 9091 Step 15: All the setups are done. Now go back to the POS and click on select hardware station and pair it with the hardware device Hope this helps!

Let’s say you need to create a new store with multiple registers on CPOS.   It is now possible to have a retail store with multiple registers each running CPOS and each having their own dedicated hardware.   For example: A store with two registers both running CPOS and both having their own receipt printer, scanner, etc. . Here comes the concept of a shared hardware station for CPOS, It may seem impractical to have multiple registers sharing the same scanner, pin pad, etc but it is actually possible.   You’ll need to install a hardware station per CPOS and then you should be good to go.   Sharing hardware can be handy in scenarios with limited space or lesser sales persons moving around taking the sales and so on and it’s valid for CPOS.   Note: However, for MPOS you need a dedicated hardware.   Please notice that you can’t have multiple hardware stations installed on the same machine. Please do correct me anyone if that has changed 🙂 This can be done absolutely and is perfectly possible. Just deploy a Hardware station on each device and it will work as discussed in the example above.

Hi, In this blog I am going to illustrate how to get past the printing issues when you are trying to print Customer order, Quotation etc. Let’s consider a scenario: You are using a POS printer which is connected to your CPOS system. After finishing a transaction you want to print the receipt again from the ‘Show journal’ tab. When you go to show journal and attempt to print a order receipt you get following error Here, you dont need to panic and start troubleshooting the hardware station. The issue may not be with the hardware station but with receipt itself.  The issue is when you attempt to print a receipt from show journal sometimes it displays large receipt format such as the below one. Now this receipt will not print from the POS printer such as Epson and is bound throw an error. Hence you get hardware station error. However there is a way to resolve this. You can switch to a small receipt format by direction keys button located on the bottom right of the page. After switching to a smaller receipt format, you can go ahead and print it easily with POS Printer. Hope this helps!

Microsoft Dynamics Nav Integration is one of the most popular ERP solutions that most of the medium and large enterprises use today. It is an ERP solution that is not only easy to learn but is easy to learn and implement. Your staff is going to become a lot more efficient when they use this ERP solution.  Microsoft is one of the best companies in the world for all the right reasons. This software contains some of the best and unique features that will not only raise the productivity of the staff but will also improve your performance. But, if enterprises want to enjoy the benefits that come from this ERP solution, they need to plan on upgrading Dynamics NAV to a cloud-based environment. Introduction: Working with failed Scheduled Jobs can be a tiresome process. This is exactly the case where one of my clients has an Invoicing & Payment Jobs which run once a day and Job Queue Entries fail to trigger these Jobs. No Errors in the Logs, No Execution Entry, Simply No Way of Figuring it out as to why Job didn’t trigger. Contacting Microsoft Support, they are asking to simply Upgrade the Application to the latest version. Which is not a preferred option as the database size is around 200GB. Let’s see how to resolve this in a smarter way. Pre-requisites: Microsoft Windows Task Scheduler Microsoft Windows Powershell Microsoft Dynamics NAV(Administration Module for PowerShell & Development Environment) Books & References: https://docs.microsoft.com/en-us/powershell/module/microsoft.dynamics.nav.management/?view=businesscentral-ps Demonstration: 1. Building Objects to Run through a Codeunit: As you know that Job Queue Entries support Reports and Codeunits and NAV Administration Module only supports Codeunit. So, in order to make it work, create a Codeunit to execute all the Reports and code units. 2. Creation of PowerShell Script: This PowerShell Script executes with the help of NAV Administration to Run the Codeunit. Prior to running the script, you need to set the Execution Policy. Syntax: Invoke-NAVCodeunit <Codeunit No.> – ServerIntance <ServerInstanceName> -CompanyName  <Company Name> -Force 3. Setting Up Task Scheduler Triggers: By Setting up the Triggers, you can decide recurrence to execute the Codeunit. It can be Hours, Daily, Weekly, Monthly, One-Time or Infinite. You can also set the time for precise execution. 4. Setting Up Task Scheduler Commands: Whenever we execute the PowerShell Script through CMD, we run the commands as follows. Command: PowerShell.exe <PS Script File Path> Here, we pass the PowerShell.exe into the script and PS Script File Path as a Parameter. Conclusion: Thus, using NAV Administration Module, Power-Shell and Task Scheduler I was about to replicate Job Queue Entries functionality. Although this works perfectly for NAV and Business Central – On-Premise, it works for Business Central on SaaS. In my upcoming blog, I’ll also show we can achieve this. Hope you guys find this blog useful 😇