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

Introduction In the field of stock management, keeping precise stock levels is essential to the success of your business. Two key components in achieving this are physical tracking and negative inventory control. Physical tracking keeps track of inventory movements in real time, and negative inventory control makes sure that stock levels never fall below zero, which keeps operations from being disrupted. In this first part of the blog, I will explore the theory behind these concepts, highlighting their importance in preventing stock outs. Understanding these principles is essential for effectively managing inventory in Dynamics 365 Finance & Operations. First let me explain Physical Inventory: Physical inventory involves continuously monitoring the movement of goods, including receiving, storing, and shipping. This tracking helps businesses keep an up-to-date record of their stock levels and avoid discrepancies. This is the practice of recording the actual quantities of products on hand at various locations, such as warehouses, distribution centers, and retail stores. The goal is to ensure that the recorded inventory levels match the actual quantities available, which is essential for accurate stock management and financial reporting. So, physical inventory is a critical component of inventory management that ensures businesses maintain accurate records of their actual stock levels. By implementing effective physical inventory practices, companies can improve inventory accuracy, prevent stock outs, and enhance overall operational performance. How Physical Tracking works in D365 Finance and Operations? In D365 F&O, physical tracking works by leveraging inventory dimensions, tracking codes, and item model groups to monitor and manage inventory accurately. Physical tracking in Dynamics 365 Finance & Operations helps you monitor and manage the actual stock of items in real-time. You can define what you want to track (e.g., batch numbers, serial numbers) and then assign these dimensions to item model groups to specify how tracking is applied. In short Physical tracking ensures that you always have an accurate view of your inventory by recording and updating item details as they move through your supply chain. Physical Negative Inventory: Physical negative inventory occurs when the recorded quantity of items in your inventory system drops below zero. This situation arises when more items are issued or sold than are actually available in stock. For example, if your system shows you have 10 items in stock, but you issue 15 items, your inventory record will show a negative quantity of -5 items. In Dynamics 365 Finance & Operations, you can control this by setting parameters that prevent negative inventory from being recorded. If you disable the option for allowing physical negative inventory, the system will only permit transactions if there is enough stock on hand. This helps ensure that your inventory records are accurate and reflect the true quantity of items available, preventing potential issues such as stock outs or discrepancies between physical stock and system records. How Physical Negative Inventory works in D365 Finance and Operations? In Dynamics 365 Finance & Operations, physical negative inventory refers to how the system manages inventory levels when they fall below zero. If you allow negative inventory, the system permits transactions even if the stock levels go below zero, which can happen if more items are shipped or adjusted out than are available. To control this, you can configure settings in the system: by navigating to Inventory Parameters and Item Model Groups, you can choose whether to permit or prevent negative inventory. When negative inventory is disabled, the system ensures that transactions only occur if there is sufficient stock, preventing inventory records from showing negative amounts. This helps maintain accurate inventory records and avoids potential issues like stock outs. Regular cycle counts and inventory adjustments are also important to keep the system aligned with actual stock levels and address any discrepancies. Conclusion Dynamics 365 Finance & Operations (D365F&O) helps businesses keep track of their inventory and prevent stock issues in a simple and effective way. For physical tracking, D365 F&O uses inventory dimensions like site, warehouse, batch number, and serial number. This means you can always see where your items are and how many you have in real-time, which helps avoid mistakes and keeps your operations running smoothly. To control negative inventory, D365 F&O lets you set rules to stop inventory levels from dropping below zero. You can find these settings in Inventory Management and Item Model Groups. If you choose to prevent negative inventory, the system will block any transactions that would cause your stock to go below zero. This ensures your inventory records stay accurate, and you don’t run into issues like running out of stock or having financial discrepancies. Additionally, D365 F&O supports regular cycle counts and inventory adjustments. These regular checks help ensure that the actual physical stock matches what’s recorded in the system, allowing you to correct any differences quickly. With these features, D365 F&O makes it easy for businesses to manage their inventory accurately and efficiently, supporting better decisions and smoother operations. That’s it for this part of the blog. In the next part, I will walk you through the process with examples, including products tracked by Serial Numbers and Batch Numbers. I will also explain how these features impact inventory transactions. 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 Business Central, processing a customer refund is a simple yet important task that ensures accurate financial management and customer satisfaction. Whether a customer has overpaid or requires a refund for another reason, Business Central provides a straightforward process to handle these transactions efficiently. In this guide, we will walk you through the steps to issue a refund, including verifying customer details, applying the refund, and processing the payment. Steps to Process the Refund Issuing a refund in Dynamics 365 Business Central is straightforward, but it’s important to ensure you select the correct document type. 1. Verify the Customer: Start by confirming the customer who will receive the refund. Access the customer list and click on the balance amount to view the customer ledger, which displays only the open or outstanding items. Note the customer number and the amount to be refunded. 2. Navigate to the Payment Journal: Open the Payment Journal and select the appropriate batch to use. Add a line for the refund to the customer, ensuring that the Document Type is set to “Refund.” 3. Apply the Refund: To apply the refund to the outstanding payment, click on “Apply Entries” in the Action Bar. Select the line you want to apply the refund to, then click on “Set Applies-to ID” in the Action Bar. This will fill in the Applies-to ID field for the chosen line. Click OK to close the page. 4. Process the Payment: Finally, process the payment. Whether you’re using a computer check or an electronic payment, follow the same steps as you would for paying a vendor. Once everything is completed, post the payment. 5. Customer ledger entry for the refund showcased above Conclusion Processing customer refunds in Dynamics 365 Business Central is a straightforward process that enhances financial accuracy and customer satisfaction. By following the outlined steps—verifying customer details, applying the refund, and processing the payment—you can ensure that refunds are handled efficiently and correctly. 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 Tasks, reports, and batch processes can occasionally take a very long time to finish. Businesses frequently make use of Business Central‘s background processing capabilities to keep employees working in the meantime. If something goes wrong and an important background process stops, or isn’t scheduled for some reason, being notified of the issue can help you react quickly to resolve it. Pre-requisites Business Central on Cloud References Get notified about issues with job queue background processing | Microsoft Learn Configuration and Feature overview To stay informed about issues with job queue processing, you can subscribe to external business events triggered under the following conditions: – Job queue processing fails after multiple retries. – Job queue processing fails to schedule. These external business events can be captured using the “When a business event occurs” trigger in a Power Automate flow. For added flexibility, we’ve included a couple of pre-built Power Automate templates with this feature. You also have the option to create a custom Power Automate flow to tailor a notification system that suits your business needs. For example, you can: – Notify the user whose credentials are used by the job queue. – Notify recipients specified in the Business Central admin center. Additionally, new job queue APIs enable automation to address specific job queue issues by restarting or rescheduling the job queue. Conclusion In conclusion, this feature offers a robust solution for monitoring and managing job queue processing issues. By subscribing to external business events and utilizing Power Automate flows, you can ensure that critical notifications are promptly delivered to the right individuals, enhancing your business’s responsiveness. With the added flexibility of built-in templates and customizable flows, along with the new job queue APIs, you have the tools needed to efficiently address and mitigate job queue disruptions, ultimately improving operational reliability.

Introduction Finance and Operations provides two major ways to interact with tables (or data entities) for external system using APIs; namely Custom Services and Data Entities. Data entities in D365 Finance and Operations simplify data management by grouping data from multiple tables. They make it easier to import, export, and integrate data with other systems. Custom services in D365 Finance and Operations allow developers to create web services for specific business needs. They enable external systems to interact with D365 F&O by exposing custom logic and operations. This helps in integrating and automating processes with other applications. In the previous blog, we saw how we can use Data Entities to create APIs.In this blog, we’ll see how we can use Custom Services to create APIs. References Custom Service DevelopmentExposing an X++ Class as a Data Contract Using Data Contracts Pre-requisites Configuration Right click on the project and click on “Add” and then “New Item” Click on Services and select the “Service Group.” Add the appropriate name for your Service Group.Do note that this will be a part of your endpoint url. Once that is done, we’ll need to create a new Service as well.Repeat the same steps but this time select the “Service” object and add the appropriate name. Once both the Service Group and Service objects are created, we’ll need to create request, response and request processing objects. For that, click on Right Click on Project > Add > New Item > Code > Class. Add the appropriate name and click on “Add”. In the Request object, set the attribute [DataContract] at the class level and add Global variables which will be used to send data to the processing object. In the Response object, set the attribute [DataContract] at the class level and add Global variables which will be used to return data from the processing object. In the processing object, write the necessary logic. Here, I’m writing the logic to pull the data from the request object into local variables and then create a Customer record along with an address entry for that customer and if everything is completed successfully, I’ll return a “Success” status along with the customer Id else a “Failed” status along with the Customer ID. If there is any logic for logging, that can be added to our processing class after the main operation has completed.You can do that in the following way –  Once this is done, we can now add our processing class to our Service object. Open the “Service” object and set the “Class” field to the processing class you have created. Right click on the Service object in the designer and click on “New Service Operation” In the new Service Operation that is created, set the method from the processing class that you want to call in the “method” field.Set the appropriate name for that method. (This will be part of the endpoint)Set the operational domain, whether it will only work for a particular company or accross the companies.Set the Access Level (Access level increases as you go down the list) Now after this, we’ll assign our Service object to the Service Group. Open the Service Group in the designer, right click it and then click on “New Service” In the newly created “ServiceGroupService” entry set your “Service” Then after rebuild, Sync database and deploy; open postman and add the following URL template. <base_url>/api/services/<ServiceGroup>/<Service>/<Method> Now, if I trigger the “Post” request, I’ll get a “Success” status along with the CustomerId.If I try to recreate the same customer, I’ll get a “Failed” status along with the CustomerId. If you are not sure whether your API exists or not, then you can simply call a “Get” request on the URL – <base_url>/api/services This returns a list of all the “Service Groups” present in the system. We can then call a “Get” request including this “Service Group” into our URL. This returns a list of all the “Services” present in the system for that “Service Group”. We can then call a “Get” request including this “Services” into our URL. This returns a list of all the “Operations” present in the system for that “Service Group”. We can then call a “Get” request including this “Operation” into our URL. This returns the Request and Response objects for this Service Operation. Conclusion Thus, we saw how to create APIs using Custom Services in Finance and Operations. In the next blog, we’ll see some advanced API functionalities that are present in Finance and Operations. 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