Managing item purchase prices effectively is crucial for accurate cost control in Microsoft Dynamics 365 Finance & Operations (D365FO). One of the key features that impacts how item prices update is the Latest Purchase Price Parameter. When enabled, this parameter ensures that an item’s price is updated based on the most recent purchase cost recorded in a Purchase Order (PO). This means that every time a new PO is created, the item’s purchase price can change depending on the most recent cost price recorded in the system. In this blog, we will explore:The impact of enabling the Latest Purchase Price parameter.Step-by-step instructions to activate this parameter.How to track price changes using Last Price History. Impact of Enabling the Latest Purchase Price Parameter Key Effects of Enabling This Parameter:The purchase price of an item in the Item Master updates automatically based on the latest purchase price in a PO.This applies to both fixed and variable pricing models.If multiple POs are created for the same item at different prices, the purchase price will fluctuate accordingly.The updated purchase price will also reflect in the Manage Cost > Item Price section. Example Scenario: Steps to Enable the Latest Purchase Price Parameter in Released Products Step 1: Navigate to Released Products Step 2: Select the Product Step 3: Enable the Latest Purchase Price Parameter Step 4: Set Initial Price in Product Master Step 5: Create a Purchase Order (PO) Step 6: Update the Purchase Price Step 7: Confirm the Purchase Order Step 8: Post the Product Receipt (GRN) Step 9: Invoice the Purchase Order Outcome:Once invoicing is complete, navigate to the Product Master and open the product. If the Latest Purchase Price parameter is enabled, you will see that the purchase price has been updated from 50 USD to 100 USD, reflecting the latest purchase cost. Additionally, under Manage Cost > Item Price, the updated purchase price of 100 USD will be visible. How to Enable Last Price History in Dynamics 365 To track purchase price fluctuations over time, you need to enable the Last Price History feature. Steps to Enable Last Price History: Outcome:Once enabled, you can view historical purchase price changes in the Item Price section, helping businesses analyze pricing trends and make informed purchasing decisions. To conclude, enabling the Latest Purchase Price Parameter in D365FO ensures that item prices remain current based on the most recent purchase cost. This feature is beneficial for businesses managing fluctuating costs and needing accurate pricing in their procurement process. Additionally, by enabling Last Price History, organizations can track price variations over time, ensuring better cost analysis and decision-making. By following the steps outlined in this blog, you can optimize your item pricing strategy and enhance financial accuracy in Dynamics 365 Finance & Operations. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com. Need further assistance? Feel free to leave a comment or reach out for expert guidance on pricing configurations in D365FO! Thank you for reading!

Microsoft Dynamics 365 Finance & Operations (D365 F&O) is a powerful enterprise solution that helps businesses streamline their operations. However, troubleshooting issues in D365 F&O can be challenging if the root cause isn’t visible on a form. One of the most effective ways to diagnose problems is by connecting to the UAT (Sandbox) database and querying tables directly. This blog will walk you through: How to retrieve SQL connection details from LCS (Lifecycle Services) How to enable firewall access to allow a secure connection How to connect to the D365 UAT database using SQL Server Management Studio (SSMS) Why Connect to the UAT Database? Diagnose Issues: Querying the database allows you to inspect data and troubleshoot errors that aren’t visible in the front-end UI. Microsoft-Managed Environments: In sandbox/UAT environments, remote desktop access is restricted, making database queries essential for analysis. Test Before Deployment: Ensures that all configurations and data changes work as expected before going live. Step 1: Retrieve SQL Connection Details from LCS To connect to a D365 F&O UAT database, you must obtain SQL connection details from Lifecycle Services (LCS). Follow these steps: Go to Lifecycle Services (LCS): Select Your Project: Find the UAT Environment: Request Database Access: Find Database Connection Info: Step 2: Enable Firewall Access for Your IP Address By default, the D365 UAT database is secured behind a firewall. You must add a rule to allow access from your machine. Go to the LCS “Full Details” page for your UAT environment. Select: Maintain > Enable Access. Add a Firewall Rule: Note: The firewall rule expires after 8 hours, so you may need to re-add it later. Step 3: Connect to the UAT Database Using SQL Server Management Studio (SSMS) The best tool for connecting to the database is Microsoft SQL Server Management Studio (SSMS). Launch SSMS and Open the Connection Dialog Enter Connection Details from LCS Set Database Name in Connection Properties Click ‘Connect’ to Establish the Connection Key Takeaway Direct Access to Data: Enables in-depth troubleshooting by querying database tables directly. Secure and Controlled Access: LCS-managed firewall rules ensure data security. Easy Setup: The process takes only a few minutes to complete. By following these steps, you can quickly and efficiently connect to your D365 F&O UAT database and retrieve critical data for testing and issue resolution. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com. Need help troubleshooting your D365 environment? Let us know in the comments!

Microsoft Dynamics 365 Finance & Supply Chain (D365 F&SC) is a powerful enterprise solution designed to optimize business operations. To enhance workflow management, Microsoft has introduced a new feature that allows organizations to set up a dedicated email ID for users to receive workflow-related notifications. This feature, available in the Feature Management area of D365 F&SC, helps streamline communication and ensures that important workflow notifications reach the right users efficiently. In this blog, we will cover:✔ How to enable this new feature.✔ How workflow notifications are managed.✔ Practical use cases, including an Accounts Payable example.✔ The key benefits of this enhancement. Enabling the Alternate Email Feature for Workflow Notifications To activate this feature, follow these steps: Outcome: Once enabled, all workflow-related emails will be sent to the email ID specified in the Alternate Email field. Managing Workflow Notifications with the Alternate Email Field Key Aspects of Workflow Email Management: Primary Email for Notifications: Fallback to Sender Email Field: Use Case: Accounts Payable Email Alias for Payment Advice Notifications Scenario:An organization uses ACH payments to pay vendors, and the Accounts Payable (AP) team wants to send payment advice notifications from a shared email alias rather than their personal email IDs. Solution Using the Alternate Email Feature: Set the Sender Email field to the Accounts Payable email alias (e.g., ap@company.com). Configure individual user accounts to use their personal email under the Alternate Email field. As a result, vendors will receive payment advice emails from the Accounts Payable alias instead of a user’s personal email. Benefit:This approach improves consistency in external communications and ensures that vendors recognize the payment notifications as coming from the official Accounts Payable department. Key Benefits of the Alternate Email Feature Simplified Workflow Management Increased Efficiency Better Team Collaboration Improved Vendor Communication To conclude, the Alternate Email ID for Workflow Notifications feature in D365 Finance & Supply Chain is a game-changer for businesses looking to enhance workflow management. By enabling this feature, organizations can streamline communication, improve collaboration, and reduce email clutter for users. With this new enhancement, users can efficiently track their workflows without the hassle of checking multiple email accounts—leading to greater productivity and better business operations. Need assistance implementing this feature? Let us know in the comments or reach out for expert guidance! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Introduction When setting up trade agreements in Dynamics 365 Finance & Operations (D365FO), you may notice the “Find Next” option. What does this Find Next flag do? How does it affect discount calculations in the system? This blog will break it down with a simple example! What Does “Find Next” Do? Find Next = ON → The system accumulates multiple applicable trade agreement lines and applies all eligible discounts. Find Next = OFF → The system only applies the first best-fit discount and ignores other possible discounts. Key Impact: When enabled, multiple discounts can be combined. If disabled, only the most specific discount is applied. Step-by-Step Example: Trade Agreement with “Find Next” Let’s walk through a real-world scenario to see how this setting changes discount application. Step 1: Create a Trade Agreement Step 2: Add Discount Lines We add three discount lines for Item A: Line Condition Discount % 1 Basic discount for Item A 5% 2 Quantity-based discount (10 – 100 units) 10% 3 Quantity-based discount (101 – 500 units) 20% Scenario 1: “Find Next” is OFF (Disabled) Step 3: Create a Purchase Order Step 4: Increase the Order Quantity Scenario 2: “Find Next” is ON (Enabled) Step 5: Enable “Find Next” Step 6: Recreate the Purchase Order Step 7: How the Discount is Applied Key Takeaways Find Next OFF → The system applies only the first matching discount. Find Next ON → The system adds up multiple applicable discounts. Best Practice: Use Find Next when you want multiple discounts to be applied together. Understanding how Find Next works helps businesses configure trade agreements properly and avoid unexpected pricing issues. Need more D365 tips? Stay tuned for our next blog! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Organizations are constantly struggling with the complexities of demand and supply forecasting. The traditional methods, often dependent on manual intervention and assumption-based procurement, are increasingly becoming inefficient. These outdated processes lead to inventory overloads, high holding costs, and a significant backlog of orders, all which hamper business growth and scalability. It’s clear that businesses need a more robust, scalable, and accurate forecasting solution. This is where AI-driven demand and supply forecasting solutions come into play, offering a revolutionary approach to streamline operations and enhance decision-making. The Business Challenges Traditional demand and supply forecasting methods pose several challenges that can hamper business success: These challenges underscore the critical need for businesses to move away from manual methods and towards more advanced, automated solutions that can adapt to the ever-changing market landscape. The AI-Driven Solution To address these challenges, CloudFronts offers an innovative AI-driven demand and supply forecasting solution designed to transform the way businesses operate. Here’s how this solution can revolutionize your business: High-Level Architecture The architecture of our AI-driven forecasting solution is designed to ensure scalability, flexibility, and real-time processing capabilities. Key components include: Benefits of AI-Driven Forecasting Implementing an AI-driven forecasting solution offers numerous benefits that can significantly impact your business: Conclusion As the business landscape continues to evolve, the need for accurate, efficient, and scalable demand and supply forecasting solutions becomes more critical than ever. CloudFronts’ AI-driven forecasting solution not only addresses the inefficiencies of traditional methods but also empowers businesses to thrive in a competitive market. 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

Managing financial transactions accurately and efficiently is crucial for any growing business. The process of ledger settlements can be time-consuming and prone to errors when done manually. To address this, Microsoft Dynamics 365 Finance version 10.0.31 introduces the ability to automate ledger settlements, helping businesses streamline their financial processes. In this article, we’ll walk you through the steps needed to enable and optimize automatic ledger settlements in Dynamics 365, so your organization can save time, reduce errors, and improve financial reporting. Automating ledger settlements is a significant improvement over the manual process. The automated process works by comparing debit and credit transactions in your general ledger. It automatically matches transactions with identical accounting currency amounts, simplifying reconciliation efforts. However, it’s important to note that this feature does not support partial matching of transactions. Before enabling the Automate Ledger Settlements feature, it’s crucial to first activate the Awareness feature between Ledger Settlement and Year-end Close. This step ensures the process runs smoothly without impacting your year-end financial closing. Steps to Enable Automatic Ledger Settlements Step 1: Identify Relevant Primary Accounts Step 2: Create a Rule for Process Automation Step 3: Set up Criteria for Automation Step 4: Manage the Created Rule Once the rule has been created, you can view or modify it at any time. This flexibility allows you to adapt the automation process to changing business needs. Step 5: Verify the Automation Batch Job Ensure that the automation batch job is running correctly. Go to System Administration > Inquiries > Batch Jobs to check the execution status. Step 6: View Scheduled Executions and Results You can monitor the status of your scheduled automations and the results of settled transactions for full visibility into your financial processes. Step 7: Access Settled Transactions To view finalized ledger settlements, navigate to General Ledger > Periodic Tasks > Ledger Settlements. Conclusion By automating the ledger settlement process in Dynamics 365 Finance, businesses can reduce manual effort, minimize errors, and optimize financial workflows. It’s essential to follow the steps outlined above to ensure smooth implementation and operation. By automating your ledger settlements, your organization can save time and improve financial reporting accuracy. Take the Next Step If your organization is looking to optimize financial workflows, start by automating your ledger settlements today. For more detailed assistance or to explore additional financial automation features, feel free to contact us.

Effective task management is essential in the field of enterprise resource planning. Administrators could designate particular batch servers to a batch group with more flexibility prior to Microsoft Dynamics 365 for Finance and Operations (D365FO) introducing “Priority Based Scheduling”. This capability was not merely about enhancing capacity but also about controlling and limiting it. The Problem of Overutilization Recently, our team encountered a significant challenge. We had 98 tasks, all marked with a “normal” scheduling priority, that were able to execute simultaneously. Given that more than 98 tasks were available, all of them entered the executing state at the same time. This situation led to a 100% Database Transaction Unit utilization over a prolonged period, which is far from ideal. Such a high utilization rate can strain the system, leading to performance issues and potentially impacting other operations. In the past, this kind of issue could have been mitigated. The older batch group mechanism allowed us to limit the number of batch servers assigned to a batch group, thereby controlling the number of parallel tasks. Unfortunately, with the shift to “Priority Based Scheduling,” this direct control seemed to have been lost, leading to the problems we recently faced. Discovery of Batch Concurrency Control With the release of version 10.0.38 PU63, a new feature called “Batch Concurrency Control” caught my attention. This feature reintroduces the ability to limit or throttle the number of parallel tasks in a specific batch group. Had we been aware of this feature earlier, and had the users selected the correct batch group in their request forms, we could have limited the number of parallel tasks to a manageable number, such as 10. This would have prevented the processing from adversely affecting other users and maintained overall system performance. Activating and Utilizing the Feature After activating the “Batch Concurrency Control” feature, you will notice a new field in the batch group settings. This field is crucial for managing task concurrency effectively. Understanding the Help Text The maximum number of tasks that can run in parallel at a time for Batch Jobs in this Batch Group. This setting should be set to zero if concurrency control is not required. To completely stop all batch jobs in this Batch Group, set the value to -1. It’s important to remember that using this feature on batch jobs with more than 5000 concurrent tasks that are prepared to run could have a negative effect on batch scheduling performance. This explanation is vital. Setting the value to zero means no concurrency control, while setting it to -1 halts all batch jobs in the group. However, caution is advised against using this feature for batch jobs with more than 5000 concurrent tasks, as it could degrade the performance of batch scheduling. Implementing the Feature in Our Workflow In our operations, we now actively use this feature to manage the number of available tasks per batch group. This approach mirrors our previous strategy, where we selected only a few batch servers for a specific batch group. By doing so, we can effectively throttle the tasks and ensure a balanced load across the system. Conclusion The introduction of “Batch Concurrency Control” in Microsoft Dynamics 365 for Finance and Operations has provided us with a much-needed tool to manage and control task execution within batch groups. By setting appropriate limits, we can prevent system overloads, maintain performance, and ensure a smoother operation. 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: Ensuring user security is a crucial aspect in Dynamics 365 for Finance and Operations. To access or utilize the features of Dynamics 365 F&O, a user must have a role assigned to them. Without a role, the user will be unable to perform any actions within the system. Access levels and business processes for a particular role are determined by the duties and privileges associated with that role. In this blog post, we will explore two recently introduced features that simplify the process of comprehending and setting up customized security roles within Dynamics 365: security diagnostic and security configuration tools. Defining terms used in Security: Security Roles: – Security roles in Dynamics 365 define how users can access different modules. – The system comes with pre-defined security roles that can be assigned to users. A user has the ability to possess multiple security roles. – Data security policies can only be applied by the administrator to limit user access to data. – To gain access to Finance and Operations, it is mandatory for users to be assigned to at least one security role.  – Security roles correspond to company responsibilities and contain a set of duties required to carry out functions. Duties: – Duties correspond to tasks of a role and are part of a business process. – They are composed of privileges necessary for performing an action. – Duties can be assigned to multiple security roles and help reduce fraud and detect errors. – Segregating duties is important for regulatory compliance such as SOX and IFRS. – Default duties are provided, and administrators can modify or create new duties. Privileges: – Privileges are unit action sets that correspond to system functions. – They specify the level of access required to perform a job or complete an assignment. – Privileges refer to specific permissions granted to application objects such as UI elements and tables. – Default privileges are provided, and administrators can modify or create new privileges. Permissions: – Permissions are required for accessing functions in Dynamics 365. – Access levels are grouped for permissions to tables, fields, forms, or server-side methods. – Permissions include any tables, fields, forms, or server-side methods accessed through the entry point. Security Configuration Tool: The Security Configuration Tool is a useful tool for administrators as it enables them to create and manage security roles, duties, and privileges.  The Security Configuration Tool is a feature in Dynamics 365 that offers various benefits to users. Here are some of the benefits: Display Entry Point Permissions: The tool enables administrators to display entry point permissions for a given role, duty, or privilege. Test Security Role is a useful feature that allows users to check if a security role, duty, or privilege has been newly created or modified, without having to create a separate test user account.  Non-Permanent Changes: Changes made in the Security Configuration Tool are not permanent and must be published to take effect. Data Export/Import: Changes can be saved as a data export file that can be imported into desired environments. Full Hierarchy View: Users can access the tool by going to System Administration > Security > Security Configuration and have a full hierarchy view of roles, duties, privileges, and entry point security assignments. Duplicate Existing Roles: Users can duplicate existing roles, duties, and privileges. Various Options: The tool offers several options for performing against the currently selected role/duty/privilege, including undo/redo customizations, creating new roles, showing all levels, deleting roles, duplicating roles, copying roles, viewing permissions, and displaying the audit trail. To add a new role in Dynamics 365 with the Security Configuration Tool, you can follow these easy steps: Step 1: Select the ‘Roles’ tab and click ‘Create new’ to create a new role in Dynamics 365. Step 2: Enter the name of the new role using a different naming convention so that it is easily identifiable. Step 3: To add a new duty to a role, highlight it, go to the Duties column, and select Add references. All duties (and customs if created) will be available in the list. Step 4: You can select certain tasks, and their corresponding privileges, to be available in a role. If needed, users can remove certain tasks from the role. Step 5: To modify object permissions, go to the Privileges section. Dynamics 365 has different access levels, such as Read, Update, Create, and Delete, that determine a user’s level of access to a particular record or record type. Security roles have three types of access levels: Unset, Grant, and Deny. Step 6: Any modifications made in the user interface must be published before they are implemented. This list shows all the changes that are not yet published. Security Diagnostic Tool: The Security Diagnostic Tool is a unique feature of Dynamics 365 that empowers individuals with a security administrator or system administrator role to conduct an assessment on any form to identify the roles, duties, and privileges required to accomplish a task.  The tool provides numerous advantages to its users, including: To use the Security Diagnostic Tool, simply follow these steps: go to the Option tab, then select Page Options, and finally, click on Security Diagnostics.  This will automatically run the tool for you. Remember that the Security Diagnostic Tool is available on any form.  After the tool runs, it will generate a comprehensive list of all the roles, duties, and privileges related to that particular form.  This enables administrators to quickly identify any gaps in security and make necessary adjustments to ensure the protection of the system and its data. Conclusion: In conclusion, Dynamics 365 for Finance offers a reliable and secure role-based security system that guarantees that users have access to only the data that is necessary for them to carry out their tasks. The security roles, duties, privileges, and permissions collaborate to create a comprehensive security system that is effective.  Moreover, the security diagnostic and configuration tools make it simpler to comprehend and customize security roles in Dynamics 365. We hope you found this … Continue reading Security Roles in D365 Finance and Operation →

In inventory management, there often arises a need for flexibility, especially when dealing with orders that exceed current stock levels. Dynamics 365 Finance and Operations offers a solution to this challenge through enabling physical negative inventory.   This functionality allows organizations to create sales orders even when inventory levels are insufficient, catering to scenarios where a stock may be incoming or when manufacturing units are involved.  Purpose of Physical Negative Inventory:  Some organizations encounter situations where they must fulfil customer orders despite lacking sufficient inventory on hand. This could be due to various reasons such as pending stock arrivals or the need to initiate manufacturing processes upon order placement.   Enabling physical negative inventory facilitates the creation of sales orders under such circumstances, ensuring business continuity and customer satisfaction.  Process to Enable Negative Inventory:  Enabling physical negative inventory involves configuring settings within Dynamics 365 Finance and Operations. This can be achieved through the following steps:  Navigate to Inventory Management > Setup > Inventory > Item Model Group.  Within the Item Model Group, allow for physical negative inventory.  For further insights into this process, refer to our previous blog post on https://www.cloudfronts.com/blog/d365-enterprise/d365-finance-operations/physical-negative-inventory-dynamics-365-operations/ can provide additional guidance.  Necessary Steps to Manage Physical Negative Inventory:  Once physical negative inventory is enabled, it’s essential to adopt proper procedures for its management to maintain accuracy and efficiency.   • Ensure Availability of Physical Inventory during Shipment: Before shipping any items, verify the presence of physical inventory in stock. Only proceed with the shipment if the required items are physically available.  • Transfer Stock if Necessary: If the required stock is not available at the shipping warehouse but exists in the main warehouse, initiate a transfer process to move the items accordingly and receive that in a shipping warehouse.  • Periodic Inventory Closing: Implement regular inventory closing procedures to ensure accurate inventory valuations.  Issues Faced by Organizations if Proper Procedures Are Not Followed:  Failure to comply with the proper procedures can lead to various issues, including:  Invalid Cost Value of Items: This can result in an inaccurate inventory valuation, subsequently affecting main accounts and profit estimation.  In conclusion, by following these steps, organizations can effectively manage physical negative inventory within Dynamics 365 Finance and Operations, ensuring smooth operations and accurate inventory valuations.  We hope you found this article useful and if you would like to discuss anything you can reach out to us at transform@cloudfonts.com 

In financial management, the accurate recording and reconciliation of transactions within the general ledger stand as paramount tasks. Microsoft Dynamics 365 Finance and Operations, a comprehensive enterprise resource planning (ERP) solution, offers a feature known as General Ledger Adjustments. This feature, often overlooked or misunderstood, plays a pivotal role in addressing critical challenges associated with ledger adjustment entries due to environmental issues or data corruption. The recent discovery of the General Ledger Adjustments feature within the feature management workspace prompted a deeper exploration. However, upon enabling this feature, it became apparent that Microsoft aims to streamline and systematize a fundamental problem-solving process. Reflecting on past experiences, various challenges related to ledger adjustments surfaced: Traditionally, when encountering such issues, the path forward often involved engaging Microsoft support to delve deeper into the problem. While Microsoft proficiently identifies the root cause and initiates steps to address it in future product updates, the immediate concern revolves around rectifying the existing corrupted or missing data. The suggested workaround typically involves manual journal entries. However, this process traditionally unfolds through email communications, leading to potential discrepancies or misunderstandings regarding the specifics—such as the nature of the journal entries, relevant dates, or designated journals. The introduction of the General Ledger Adjustments feature within Microsoft Dynamics 365 Finance and Operations appears as a structured attempt to address these challenges within the system itself, streamlining and formalizing the process that was previously conducted through ad hoc communications. Enabling General Ledger Adjustments: In this section, Microsoft Dynamics 365 Finance and Operations provides an interface where recommended journal entries for data correction are populated based on identified discrepancies or issues within the system. Users are presented with suggested adjustments, and based on their discretion and analysis, they can decide to create a journal entry directly from this interface. Note: Creating a journal entry from this interface generates a “Daily” type of journal within the General Ledger, facilitating a more organized and systematic approach to handling the necessary corrections or adjustments. In conclusion, this feature signifies a proactive step towards enhancing the efficiency and accuracy of managing ledger adjustments within the Microsoft Dynamics 365 Finance and Operations ecosystem.