If you’re finding it challenging to decide when to use Azure Service Bus Queues or Topics, this blog is for you! In our previous blog, we explored Azure Service Bus Queues, Topics, and Subscriptions. To recap, Azure Service Bus is a fully managed messaging service provided by Microsoft Azure. It helps decouple and scale applications by allowing different components to communicate with each other through messages. In this blog, we will delve deeper into Azure Service Bus Queues vs. Topics, examining their differences, use cases, and how to choose between them based on your application needs. By understanding these core concepts, we’ll be better equipped to design scalable and efficient messaging solutions using Azure Service Bus. Azure Service Bus Queues vs. Topics Service Bus Queues Queues work on a First In, First Out (FIFO) basis. This means that clients that receive messages from the queue and then process that message in the order in which they were added to the queue, and they will be the only consumer that processes this message. The queue will store this message until our client is able to process them. To process the message, the client will pull the message off the queue. Purpose: Queues are designed for point-to-point communication. They are ideal when a single consumer needs to process messages from a single sender. Message Handling: Messages are stored in a queue and processed by a single consumer in a first-in, first-out (FIFO) manner. Use Case: Best suited for scenarios where a specific task needs to be handled one at a time. For example, in an order processing system where each order needs to be managed sequentially. Fig – Message Queue with Messages One of the benefits of using queues is that producers and consumers do not need to exchange messages simultaneously. Messages are stored in the queue and are processed only when the consumer retrieves them. This setup enables producers to continue sending messages to the queue independently. Consequently, components within our architecture can be decoupled, as producers and consumers are not required to synchronize their actions. If there is a high volume of messages entering the queue, we can scale up the consumers without needing to scale the producers. Service Bus Topics Topics are different to Queues since instead of working with a single consumer, we can have multiple subscribers to our topic, who will receive their own copy of the message from the topic. This works in a pub/sub pattern, where we will have messages being published to the topic and have multiple clients subscribe to that topic. Purpose: Topics are designed for publish-subscribe communication. They allow messages to be sent to a topic and processed by multiple consumers. Message Handling: Messages sent to a topic are delivered to multiple subscriptions. Each subscription can have its own filter and process messages independently. Use Case: Ideal for broadcasting messages to multiple systems. For instance, a CRM system might need to notify various departments (e.g., sales, marketing) about a new customer record. Fig – Topic with three Subscription with Messages In Topics, our consumers don’t directly consume the message from our Topic. Instead, we create subscriptions that subscribe to the topic and our consumers receive a copy of a message from the topic. In Azure Service Bus, we can define filters on these subscriptions that determine conditions for messages to be published to a subscription and actions that modifies the message metadata. Conclusion In this post, we discussed the differences between Queues and Topics in Azure Service Bus. To summarize, Azure Service Bus Queues are ideal for point-to-point communication in which messages must be handled sequentially by a single consumer. Topics, on the other hand, are suitable for scenarios that need publish-subscribe patterns, as they enable several consumers to process the same message independently. Choosing the proper solution is determined by your application’s, individual requirements, ensuring that your message system is both scalable and efficient. If your system requires sequential processing and single customers, queues are the best option. However, if your system wants to broadcast messages to several users, Topics will give the necessary flexibility and scalability. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Problem Statement  After an implementation has gone live, do we experience that the user participation tapers off before starting to decline? That’s when we feel the need to have an adoption strategy and metrics into place.  Strategizing User Adoption  Here are some thoughts on thinking about how to plan for User Adoption –   User Adoption Measurements  Here are some of the measurements and steps to take for User Adoption –   Conclusion  When you measure user adoption through trackable metrics and numbers, you can monitor the implementation’s success path.  This helps in rethinking the implementation and taking corrective action before the implementation itself is in question and why was it planned in the first place. Participation of partners, peers and all stakeholders share equal responsibility to make the implementation a resounding success.  We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

How to do Inventory closing and Recalculation? In D365 Finance & Operations, inventory closing, and recalculation are essential process and recommended to be part of the month close standard operating practices. In case these practices are not followed, companies may face issues like inventory miscalculations, inconsistent inventory values in defined dimensions. Go to Inventory Management>Periodic Tasks>Closing and Adjustment. Then from the Action tabs click on Close Procedure dropdown, in that click on Close Inventory. After clicking on the Close Inventory a dialogue box will open in that select the Closing Period Code. Then under the Post-Closing you can see the Run Recalculation after Closing parameter, enable this and then click OK for Inventory Closing. Enabling this parameter will Run the Recalculation right after the Inventory Closing. After clicking OK the system will run the Closing and Recalculation Batch Job. This is how the Inventory Closing procedure takes places in D365 Finance and Operations. What happens by Inventory month close and Inventory Recalculation: – Inventory Month Close: The system generates inventory closing journals and settlement entries for the closed transactions resulting into adjustments to update inventory accounts like inventory value and cost of goods sold. It blocks the inactive dimensions from being considered into any of the valuation process. – Inventory Recalculation: The system does an inventory revaluation to adjust inventory values based on the latest costs, market values and inventory valuation method selected (FIFO, LIFO, Weighted Average, Standard Cost). By including inventory month close and revaluation as part of the month end SOPs, companies can achieve efficient inventory management. Conclusion: Inventory closing and recalculation in D365 Finance & Operations are critical processes for maintaining accurate inventory values and ensuring smooth month-end procedures. By performing these tasks regularly, businesses can prevent discrepancies, update inventory accounts effectively, and reflect true inventory costs based on the chosen valuation method. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In Dynamics 365 CRM, integrating with external systems, running automated processes, and developing custom applications often requires non-interactive access to CRM data. One of the most secure and efficient ways to achieve this is by creating an Application User via the Azure Portal. In this blog, we’ll guide you through the step-by-step process of setting up an Application User and explain when and why you should use it in your CRM environment. Steps to Create an Application User: – Navigate to the Azure Portal and log in with your Azure account. – Search for Azure Active Directory or select from the left-hand menu. – Click on “App registrations” in the Azure Active Directory blade and click on “New registration”. – Enter the following details: – Click “Register”. – Select the newly created application from the App registrations list and click on “API permissions” in the left-hand menu. – Click on “Add a permission”. – Select “Dynamics CRM”. – Select “Delegated permissions” and check the necessary permissions such as user_impersonation. – Click “Add permissions”. – Click on “Grant admin consent for [your organization]” and confirm. – Go to “Certificates & secrets” in the application settings. – Click on “New client secret”. – Add a description (e.g., “CRM App Secret”) and set an expiry period. – Click “Add”. – Copy the value of the client secret and store it securely. You will need it later. – Add Application User in Dynamics 365 CRM – Log on to the Microsoft Power Platform Admin (D365 Admin) centre as a system administrator. – In the navigation pane, go to Environments, and then select an environment form the list. – On the Settings tab, go to Users + permissions, and then select Application users. – The application users page appears. – Click + New app user. – After clicking on + New app user. A side menu slider will appear. Here you will have to: When to Use an Application User Conclusion Creating an application user in Dynamics 365 CRM via the Azure Portal is a straightforward process that enhances the integration capabilities and automation potential of your CRM environment. By following the steps outlined above, you can set up an application user and leverage it for various integration and automation scenarios. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction When managing Opportunities in Dynamics 365, the default dialog box for closing an Opportunity as either won or lost often lacks specific fields that may be essential for your business process. Attempting to close an Opportunity as either won or lost, you will encounter the following dialog box with the following options. Curious about customizing this dialog box with additional fields? In this blog, I’ll guide you through customizing your Opportunity Dialog Box when marking it has won or lost. Steps : – Sign in to Classic Dynamics 365 using your URL, such as abc.dynamics.com, and enter your credentials. – Create a Solution and include the out of the box called ‘Opportunity Close’ table/entity. – After adding the table/entity, navigate to the forms section and include the Quick Create form for ‘Opportunity Close’. – Include the fields you need in this Quick Create Form. You can also add your own custom fields. Here, I’ve included the out-of-the-box fields. After making changes, save and then publish. – After saving and publishing your changes, navigate to the model-driven app and choose the app where you wish to incorporate the entity. – When customizing your form in Dynamics 365 the classic way, ensure to remove and re-add the Quick Create form for Opportunity Close in the Model-Driven Apps section. – Ensure that your entity is added, and all forms are included as shown below. Once saved, remember to publish your changes. – Navigate to the Dynamics 365 page and refresh it 2-3 times. You will notice that when you attempt to close the Opportunity as won or lost, the default dialog box will no longer appear. Instead, the custom Quick Create form you created will be displayed. Conclusion Customizing the Opportunity Close dialog box in Dynamics 365 allows you to gather more relevant data at critical stages in the sales process. By following these steps, you can easily modify the default form and include additional fields that align with your organization’s needs. This not only improves data capture but also ensures a more streamlined experience for your sales team. Hopefully, this guide has helped you understand the customization process and enabled you to take advantage of Dynamics 365’s flexibility. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Effective project management is essential for business success, and Microsoft Dynamics 365 Business Central provides robust tools to improve project management practices. As a functional consultant, I’ve witnessed the transformative impact of Business Central on project oversight, workflow efficiency, and overall productivity. In this blog post, I will offer insights on how to effectively utilize Business Central for successful project management. An Overview of Project Management in Business Central D365 Business Central features a wide array of project management tools that assist businesses in overseeing projects from start to finish. These resources facilitate efficient planning, execution, and monitoring, ensuring that projects are delivered on schedule and within budget. Key Features and Functionalities Practical Applications Implementation and Configuration Benefits and ROI Adopting Business Central’s project management capabilities can lead to notable improvements in efficiency and project results. Clients frequently benefit from: Conclusion Leveraging D365 Business Central for project management offers numerous advantages, from improved visibility to enhanced financial control. By taking advantage of the platform’s powerful features, businesses can streamline project workflows, optimize resource allocation, and achieve superior project outcomes. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In this blog we will learn about the basic setups required for the Advanced Warehouse Management process. These setups may vary depending on the business scenarios. For a Location Directives to work in an Advance warehouse scenario, there are some prerequisites that we need to do first. The following are the setups that we need to configure:  The Location Directive plays a significant role in inventory movement in advanced warehouses. Location Directives are the set of rules which define the pick and put, Counting, License Plate building, Status change and Quality check etc. for individual warehouse or group of warehouses.  – For my current scenario, I will create a location Directive for a Sales Order and Transfer Order transactions.  – In the work Order Type, from the drop-down menu select “Sales Orders”  – Enter the information below as per business use cases.  – Enter Location Directive name. Here I have mentioned, “SO Pick”  – Enter work type as “Pick”  – Enter Scope. Here I have mentioned for “Multiple Items”  – Enter warehouse.  – Add From and To quantity fields.  – Add location directive actions. Here I have mentioned “Fixed and Non-Fixed locations”  – I have done the same setup for Sales Order “Put”.  – Now we will do setup for transfer Order location directive.  Here, we will have to do the separate setup for Transfer Issue and Transfer Receipt.  Transfer issue:  – Enter Name.  – Enter work type as “Pick”.  – Enter scope. I have selected here as Multiple Items.  – Select the warehouse. I have selected here as All warehouses.  – Enter quantity.  – Enter fixed location usage.  Transfer receipt:  – Enter Name.  – Enter work type as “Put”.  – Enter scope. I have selected here as All Items.  – Select the warehouse. I have selected here as All warehouses.  – Enter quantity.  – Enter fixed location usage.  Here I have mentioned “Fixed and Non-fixed locations”  Now, location directives are ready to use in Advance Warehouse process.  That’s it for this blog!!  How to use these location directives in actual transactions will be discussed going forward in the blog series.  Conclusion We’ve explored the essential setups required for implementing the Advanced Warehouse Management process, focusing on the creation of Location Directives tailored to specific business scenarios. By configuring these directives, you can effectively manage inventory movements, ensuring a smoother workflow for Sales Orders and Transfer Orders. Next in the Blog series:  How to create Work Classes and Work Templates in Advance warehouse management in D365.  How to set up Worker in Advance warehouse management in D365.  We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Tracking user logins in Business Central helps you understand how your system is used. The “Register Time” feature makes it easy to see when users log in and how long they stay. This guide will show you how to set it up and check user activity. Pre-requisites Business Central (On-prem/On-Cloud) Steps Step 1: Activate the Register Time Feature Step 2: Configure Individual User Settings Step 3: Check User Login Data By following these steps, you can easily monitor how often users log in and how long they stay connected to your system. Conclusion Tracking user logins and session times in Business Central helps you understand how your system is used. By setting up the Register Time feature and checking the User Time Registers page, you can easily monitor user activity and make informed decisions to improve system performance. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Namespaces help avoid name conflicts that can arise from combining libraries by grouping code into logical groupings and hierarchies. Namespaces give the code base structure, which facilitates navigation and comprehension, guarantee uniqueness in code names, and permit name reuse in many situations. Numerous computer languages employ namespaces, and Business Central provides them with AL from Business Central 2023 wave 2 (BC23). Table Customer All objects in the code file belong to the namespace that is declared at the beginning of an AL file. Pre-requisites Business Central onCloud References https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-namespaces-overview Configuration They can be used to help avoid naming conflicts between different extensions, making it easier to maintain and understand extensions, including the relationship between different objects. Namespace syntax To declare a namespace in AL, you must use the namespace keyword followed by the name of the namespace. Some best practices for namespace keywords are: Example:  namespace DevOrg.Client.SpecificModule; You can use the same namespace declaration in other.al files to declare multiple objects in the same namespace. The same namespace is shared by all code files that employ the same namespace declaration. If you try to utilize an object after namespaces have been declared, an error will occur. Example: The error will be fixed after declaring a keyword with namespace name. Conclusion At first glance, namespaces appear superfluous and confusing, but as you use them, you’ll realize their true value and realize they’re not that complicated after all. Give them a try. These are all excellent practices that Microsoft supports as well. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Reversing a Drop Shipment Goods Receipt Note (GRN) and Sales Shipment in Microsoft Dynamics 365 Business Central can be a complex but essential task when handling errors or changes in your supply chain process. Drop shipments involve directly shipping goods from your vendor to your customer, bypassing your inventory. However, mistakes or adjustments may necessitate reversing these transactions to maintain accurate records. In this guide, we’ll walk you through the steps to correctly reverse a drop shipment GRN and sales shipment, ensuring your system reflects the necessary changes. Steps to Achieve goal: Click on the Post action and choose Receive action, which would post the negative quantity. Please Note: Conclusion By following this method, you can effectively reverse the drop shipment transactions and correct any errors in Business Central before invoicing. We hope this article was helpful to you. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com