In Dynamics 365 Finance and Operations (D365 F&O), the use of batch numbers is a common practice to manage and trace items with specific characteristics. Batch numbers are typically assigned to groups of items produced or received together, allowing for better control, tracking, and compliance with industry regulations. In this blog I will explain how to solve the expiration date issue while registering a Batch and Serial number tracked product. In the above screenshot you can see that the Batch Number 23010-CM-000088 has been assigned for my Item P-000014. Here, the Expiration Date is 08-04-2023. Now if I try to register this Item with the same Batch Number, I will get the Batch Number Expiration Date being past the Required Date error. Now to solve this error go to Inventory Management>Enquiries and Reports>Tracking Dimensions>Batches. Now on the Batch Number page go to Reset Tab then under the Reset tab click on Reset Shelf-Life Dates. The next step is to select the New Expiration Date and then Click Ok. This will Update the Expiiration Date of that Batch Number. In the above screenshot you can see that the Expiration Date has been changed. Now we will be able to register the Item. Here, you can see that now I am able to register the Item successfully. That’s it for this blog. Hope this helps you! Thank You!

Introduction: This comprehensive guide provides administrators with a step-by-step process for restoring Microsoft Dynamics 365 Business Central environments to a previous state within the retention period. Users with Restore Permissions: Only specific users, such as internal and delegated administrators, can restore environments. These users must also have the D365 BACKUP/RESTORE permission set in the relevant environment. Considerations and Limitations: Environments can be restored up to 10 times per calendar month. Restoration is limited to the same Azure region and country as the original environment. Preparation before Restoration: Before restoring an environment, it’s essential to communicate the plan within the organization, restrict user access, and consider renaming the environment to avoid conflicts. Restoration Process: 3. Click on Restore 4. In the restore environment window select date and time to which you want to restore the environment. 5. Select the type of environment such as sandbox or production. 6. Name for restored environment. 7. Click on restore. Important point: You can restore your production environment into a new production environment even if doing so results in exceeding your number of environments or database capacity quotas. You can however only exceed this quota by one extra production environment, regardless of how many production environments you have available for your subscription. This capability is provided as an exception, to ensure that you can always restore your production environment in critical situations. You must return within your quota within 30 days following the restore by either removing the original production environment or by purchasing an additional production environment. Once the data in the restored database meets your expectations, activate the users, initiate the work queues, and notify your organization that the environment is once again available for use and that the restoration procedure is now complete. Hope this helps!

Introduction: It is crucial for the management team to track the client’s utilization of the system as a key metric for assessing the project’s success and the value it brings to the client. To facilitate this monitoring process, I have developed a utility that can automatically generate and send reports to the management team, detailing the number of records created in specified tables. For example, during the initial master data upload phase, 1500 data added into the Customer table. Subsequently, over the following month, this figure increased to 1750 and then to 1950. Such trends signify that the client is utilizing the system in line with expectations. Pre-requisites: Configuration: Usage Statistics Setup Page: This page, contains two main fields:- Collect Statistics (Boolean) and Mail Recipients (which contains email id’s to which the report has to be send) and one more field that is primary key field is added in table but not in page and it is set to code due to which the header we get as required in Usage Statistics Setup Page. The datatype of the field primary key is set to header because the default number of code is null. Regex is used for pattern matching. Here, email validation is added on Mail Recipients. User can enter multiple email addresses in this format eg. abc@gmail.com;xyz@gmail.com. If the Collect Statistics is enabled than only you can process further and there should be at-least one mail id present in Mail Recipients. Usage Statistics Configuration Page: This page contains the actual data from which the data will be passed and report will be generated. The list and the card pages are also created with same fields. The “All Object With Caption” is used for viewing all object details in the system. The trigger lookup is used to get the table no. and table name at runtime. After fetching the specific table no. and table name, fields will filter according to the filter field 1 value, same goes for filter field 2 value. (filter field 2 is added according to the requirements.) The FieldsDisplay procedure is used to retrieve field no. and field name of the according to its record. In Filter Field 1 Name any field can be selected and filter field 1 value must be set according to that field. Create Statistics Report: This report is designed to automate the generation of usage statistics based on configurations specified in the “Usage Statistics Configuration” table. The report is flagged as “ProcessingOnly,” indicating it is intended for background processing rather than direct user interaction. The dataset within the report contains a data item with an “OnAfterGetRecord” trigger, which executes after each record is retrieved. This trigger is responsible for processing each configuration record, applying filters, and updating or inserting records into the “UsageStatistics” table. Additionally, the report features an “OnInitReport” trigger that checks the “Usage Statistics Setup” table to ensure that statistics collection is enabled. If this condition is not met, an error message is displayed, and the report exits. In essence, this report streamlines the creation of usage statistics in Business Central, adhering to specified configurations and ensuring the necessary setup conditions are satisfied before processing. Usage Statistics Page: After filter the number of records the data which will be generated will be displayed in this table. List will also be created with same fields. In Record Count the number of values are there which satisfies the filter condition. Send Statistics Report: This report is designed to send usage statistics via email. Let’s break down the code: The report begins with specifications such as its application area, caption, and usage category. Notably, it is marked as a “ProcessingOnly” report, indicating it is intended for background processing rather than direct user interaction. The OnInitReport trigger executes when the report is initialized. It checks settings in the “Usage Statistics Setup” table, ensuring that statistics collection is enabled (“Collect Statistics”) and valid mail recipients are specified (“Mail Recipients”). If these conditions are not met, error messages are displayed, and the report exits. The main functionality is in the OnPostReport trigger, which executes after the report is processed. It performs the following steps: Email Excel Sheet: In this, on 22nd date after applying the filters the output is given and on 24th it again checks by applying same filter since new data was not added in the respective table that’s why it is showing the same data. Conclusion In conclusion, the automated reporting tool plays a pivotal role in monitoring client system utilization, revealing encouraging trends such as the gradual increase in customer records. These insights affirm the project’s success and underline its value to the client, reinforcing our commitment to proactive monitoring for continual optimization and client satisfaction.

Hello Everyone!!! In this blog I will explain the Quarantine Management process in Dynamics 365 Supply Chain Management.  Here the Product was first received in the Main warehouse and then it was moved to Quarantine Warehouse for further inspection as the Product failed to clear the Quality Test. In this blog I will explain a scenario where the Products should be directly received in the Quarantine Warehouse for inspection and after final inspection it turns out that all the products fail the inspection so, a few products will be scrapped and the rest will be returned back to vendor. What is Quarantine Management? The quarantine management process in D365 aims to effectively manage and control quality issues, ensuring that only items meeting the required standards are released for use or distribution. The quarantine management process in Dynamics 365 is a systematic approach to handling items that are suspected of having quality issues or non-conformities. When an item is flagged for quarantine, it is physically segregated from the regular inventory and moved to a designated quarantine location. The quarantined item undergoes thorough inspection and testing to assess the extent of the quality issue. Based on the evaluation, decisions are made regarding the item’s disposition, which may include repair, return to the vendor, or scrapping. If the item is repairable, necessary actions are taken to rectify the identified issues. In cases where the vendor is responsible, the item can be returned for resolution. Once the necessary actions are completed, and the item meets the required quality standards, it is released from quarantine and reintegrated into the regular inventory for use or distribution. This process ensures that only items meeting quality criteria are allowed for further processing, while mitigating the risk of non-conforming products entering the supply chain Let’s start with the setups first: Step 1: Map the Quarantine Warehouse to the Main Warehouse. For that the Pathway is: Go to Inventory Management>Set Up>Inventory Breakdown>Warehouses. Step 2: The next step is to Enable the “Quarantine Management” parameter in the Item Model Group Quarantine Management Process: The below Purchase Order CM-PO-0000137 has been received in the Quarantine Warehouse as per the setup, hence a Quarantine Order CM-0000142 with 9 quantities has been created. Now if I go to the Quarantine Orders page, I can see that a new Quarantine Order has been created. The below screenshot shows the Transactions that took place after the Product Receipt was posted. After Inspection it was found out that 5 quantities were damaged, 4 quantities were to be returned back to the Vendor which means that all the 9 quantities failed to pass the Quality Inspection. So, what I will do is Scrap the 5 quantities and return back the 4 quantities to the Vendor by creating a Purchase Return Order.  Now I will split the Quarantine Order CM-0000142 into 2 separate Quarantine Orders. For that I will use the Split function which is available at the Top of the screen under the Functions Tab. In the above image you can see that I have split the Quarantine Order CM-0000142 into 2 different Quarantine Orders that is CM-0000143 and CM-0000144 for further processing. Now let’s begin the further processing. To scrap this order, I will use the Scrap functionality. To Scrap this order, click on Function and then select Scrap. Here, you can see that the Quarantine Order CM-000143 has been ended as it has been scrapped. 2.  Return the Items back to vendor: Now in order to return the Items back to vendor I will first the Invoice the existing Purchase Order which is CM-PO-0000137. Then I will receive the Items from the Quarantine warehouse to the W3 warehouse. Below you can see that I have invoiced the purchase order CM-PO-0000137. Now let’s receive the items from the Quarantine Warehouse to the Central Warehouse, for that I will use the Arrival Journal. As you can see that a New Arrival Journal has been created. Validate and Post the Journal. Vendor Return Process: After posting the Journal create a New Purchase Order with the type as Return Order.  For that go to Procurement and Sourcing>Purchase Orders>All Purchase Orders. Then select the Vendor to whom the Items will be returned and select the Purchase Type as Return Order. Enter the Site and Warehouse from which the Items will be returned back to the Vendor. Then enter the RMA number provided by the Vendor and then Click OK. Click on the Purchase Order line, select Credit Note, choose the specific invoice, input the quantity as a negative value, and then click OK. In my case the Invoice Number was 311711, so I will select that and then click OK. Then proceed with the normal purchase order processing which will be Product Receipt and Invoicing. After Invoicing the Return Order aa credit note will be  created which will be  deducted from the Vendor Balance. The below screenshot represents the On hand List before and after posting the Return Order Invoice. In the above screenshot you can see that the On hand Quantity changed from 26 to 22 since 4 quantities have been returned back to vendor. That’s it for this blog. Hope this helps you! Thank You!

Hello everyone! Shopify has become a powerful platform for companies to build their online presence and run their operations in the e-commerce space. Effectively maintaining consumer data is one of the most important aspects of running an online shop. In this article, we’ll show you how to build a custom connection to use a Postman collection to extract a single customer’s information from Shopify. You may easily get client information using this simplified procedure for better customer service and data analysis. Let’s get started! Click this link ‘https://documenter.getpostman.com/view/3800273/SWLk55pF’ to get the Postman Collection. Click ‘Run in Postman’ button, select ‘Postman Desktop App to Import’ and select ‘Open App Make sure Postman is installed in your device. Once this is imported, you will see the pre-built libraries. Export the Postman Collection and Select ‘Customer’ Imported the Collection which is exported which is in the swagger.json format Add an image as the connector icon and description as shown below. Add the host name and move to the next Section ‘Security’ Select a type of Authentication. Here, in this case, I selected Basic Authentication. Basic Authentication involves Username and Password. Provide appropriate parameter labels. We can see the pre-defined Actions as we imported the postman collection. We will be retrieving details of a single customer so select ‘RetrievesASingleCustomer’. Enter the verb Get request URL to retrieve the single customer detail Verb: GET, URL: https://{apikey}:{password}@{hostname}/admin/api/2020-10/customers/{customer_id}.json Paste this: Like this:https://8b3340489beedff0d96efe51699060e2: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@cassrodshop.myshopify.com/admin/api/2023-01/customers/{customer_id}.json Here, {customer_id} is the input parameter. So, I have edited and pre-defined the Customer ID value. Click on Create ‘Custom Connector’ Add a new connection to test the connection. Enter the API Key as the Username and Admin API Access Token as Password. You will find this in your Shopify environment Developer Options. A connection is displayed here. If it doesn’t reflect, refresh the Connection. Add the Customer ID here and click ‘Test Operation’. Voila, the response is successfully generated. Hope this helps!

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.

In the dynamic landscape of manufacturing, retail and distribution, the selection of the right Warehouse Management System (WMS) holds paramount importance. It’s a pivotal decision that influences operational efficiency by saving time and labor in tracking processes, reducing loss of inventory, prevents loss of sales opportunities, greater productivity & stock control. Hence resulting into greater customer satisfaction and ultimately, business growth. Among the plethora of available options, two prominent choices stand out: D365 F&O out-of-the-box WMS solutions and SATO Global WMS. Out-of-the-box WMS solutions in D365 Finance and Operation offers standardized features designed to suit general warehouse management needs. These solutions are pre-configured and cater to businesses that prioritize simplicity and adherence to standard industry practices. Advantages of D365 F&O Out-of-the-Box WMS: Conversely, SATO WMS along with D365 F&O ERP: SATO WMS is 3rd party software which is tailored for customization and efficiency. SATO WMS is renowned for its adaptability and tailored functionalities. It offers a high level of customization, empowering businesses to mold the system according to their unique requirements. This flexibility facilitates seamless integration with existing processes, ensuring a smoother transition and optimized operations. Key Features of SATO WMS: The decision between SATO WMS and out-of-the-box WMS hinges on understanding the specific needs and priorities of the customer. If a customer prefers standardized processes and does not require extensive customization, an out-of-the-box WMS might be more suitable, offering a cost-effective and efficient solution. However, for businesses seeking a highly customizable solution to align with their unique operational workflows, SATO WMS stands out as the preferred choice, providing adaptability and tailored functionalities that enhance efficiency and productivity. Conclusion: Selecting the right WMS is a critical decision that directly impacts operational efficiency and business growth in the manufacturing, retail and distribution sectors. While SATO WMS offers unparalleled customization and flexibility, out-of-the-box solutions excel in providing standardized, cost-effective options. By comprehensively evaluating factors such as customization needs, operational workflows, scalability, and budget constraints, businesses can make an informed decision that maximizes efficiency and drives growth.

In today’s fast-paced business environment, efficient workflow management is essential for organizations to stay competitive.  Workflow email alerts help organizations stay on top of important business processes by automatically notifying designated individuals when certain tasks are completed or when specific conditions are met.  In this article, we will provide a step-by-step guide for setting up workflow email alerts in D365 FO. Before getting started, it’s important to ensure that email parameters are configured correctly and that you are able to receive test emails from D365 in your inbox.  To check this, navigate to System Administration> Setup > Email > Email Parameters.  1. In the configuration, Enable the email provider as per your requirement.  2. If your using the SMTP setting then enter the outgoing server information, and SMTP port and enable SSL/TLS required button. Set up an email address for the user who will receive alerts and enable workflow email alerts for that user. To accomplish this, go to the System Administration section, select Users, and then click on Users. Highlight and click on the user you wish to enable email alerts for.  If no email address is attached, enter the user’s email address. To enable email notifications, go to ‘User options’ on the ribbon, then click on ‘Workflow’ on the left side and set the option to ‘Send notifications in email’ to Yes. Create an email template or email message. Templates are generic and can be configured while configuring workflows.  Navigate to System Administration> Setup > Email> System email templates. Here you can create a template, such as “Workflow emails.” Assign your email template to the specific workflow. To configure the workflow email alerts, you can navigate to the workflow for which you want to send email notifications, Open that workflow access the basic settings, and choose the relevant workflow template from the dropdown menu. Configure the necessary notifications for the particular task, control, or approval while setting up the workflow steps. Here, you will specify the notification content which will be sent to the user in the email. Configure the batch job to distribute the email notifications. Navigate to System administration > Periodic tasks > Email processing > Email distributor batch.  Since we are now adding a batch job, it can be scheduled to run automatically at specified intervals. To schedule autorun, adjust the ‘Recurrence’ settings as per the requirements. Monitor email sending status. To access the E-mail Sending Status page, go to System administration > Periodic tasks > Email processing > Batch email sending status.  Here, you can monitor successfully sent, pending, or failed email messages. In conclusion, configuring workflow email notification alerts can be a simple yet effective way to stay on top of important business processes.  By following the above steps, you can set up workflow email alerts in D365 FO and start reaping the benefits of streamlined workflow management. Thank you for reading my blog!

Introduction: In this blog I will demonstrate the set ups for opportunities. The sequence for setting up opportunity to sales cycle is as follows: Opportunities: Any inbound lead could be viewed as a potential sales opportunity. You can make opportunities and link them to certain salespeople to keep track of possible sales. You must first build up sales cycles and sales cycle stages before you start working with opportunity management. When creating opportunities, you should include details such as the contact, salesperson, sales cycle, and dates as well as your estimates of the opportunity’s sales value and success odds. Set up Opportunity Sales cycle Codes: Set up Opportunity Sales cycle Stages: On the Sales Cycles page, select the line for which you want to set up stages, and then choose the Stages action. The Sales Cycle Stages page opens. Stage: Specify the stage number. Description: A description for particular stage Completed %: Specifies the percentage of the sales cycle that has been completed when the opportunity reaches this stage. Chances of Success %: Specifies the percentage of success that has been achieved when the opportunity reaches this stage. Activity Code: User can select the activity Code for particular stages. (Activities have to be created separately) Quote Request: this check box puts a validation on that particular stage to request quote. Allow Skip:  this check allows user to skip that stage. Date Formula: Specifies how dates for planned activities are calculated when you run the Opportunity – Details report. Comment: Specifies if comments exist for the selected stage. (To add comment on any stage, navigate to Related –> Sales cycle –> Comments) Set up activities with task: You can combine multiple task, in an activity. A task represents a step in the activity. You can assign activities to opportunities, salespeople, or contacts. Assign tasks or activities of tasks to opportunities. The following procedure describes how to assign activity tasks to opportunities. The steps are similar when you assign tasks to salespeople and contacts. I will be demonstrating how to create Opportunity and Process sales Opportunities in part 2. Hope this helps!

In every organization, all kinds of expenses and revenues are tracked under dimensions like cost centers, departments, employees, etc. It is often a business requirement to split expenses or incomes in fixed proportions between two or more dimensions for accurate reporting.  On the other hand, it may be required to assign a dimension only on one GL account, restricting it from others. D365 Finance offers a smooth, flexible and a very easy process to fulfill both kinds of requirements to achieve accurate reporting of the organization’s P&L from a dimension standpoint. The blog assumes the reader is already aware about setting up financial dimensions and using them for regular transactions so the point of focus will be on the advanced features only. The procedures for both requirements are as follows: – Let’s assume that an organization tracks all kinds of office expenses in two dimensions – department and cost center. The organization wants to split the cost in a 70:30 proportion between both. In order to do that, we will use Ledger Allocation Journals. Path – General Ledger -> Allocations -> Ledger Allocation Rules The source defines the main account that will be used to split the amount. The Destination defines the dimensions and the proportion in which the amount will be split between them. In the General tab, we define the validity date for which the rule will be active. The allocation method defines the various methods in which the GL amount can be distributed. Most often, the splitting is in fixed percentages. Turn the Active checkbox to activate the rule. In the source, define the main account. In Destination, define the percentages of distribution. From the above image, we are using a 70:30 distribution ratio between Cost Center and Department.  Here, we have defined a default dimension so that the system will know how to distribute the amount between the cost center and the department only. It will ignore any other dimension. If the default field is left blank, then the user will have to manually select the dimensions at the time of the transaction. In the first distribution, a fixed percentage of 30% is applied to the Cost Center. Create a new distribution again and allocate the remaining 70% to a department dimension. In this example, we are using only 2 dimensions, but the user may define as many distributions between multiple dimensions as required as long as the percentages add up to 100%. Save the rule and close it. Now, create any regular transaction with the GL account, like a general journal. Select the dimensions for the cost center and the department as shown above and post the document. Once posted, go to General ledger -> Ledger Allocations -> Process Allocation Request. Select the allocation rule. In the field Proposal Options, there are two options: – The first option will directly post the entry and allocate it to the dimensions. The second option will keep the entry unposted so that the user may verify the dimensions or make changes to them manually if required. It is always preferable to select the second option. Upon clicking Okay, the system will create an allocation journal as shown below: – Upon clicking open the allocation journal, the accounting impact is shown as below: – The accounting impact can be summarized below as follows: – GL Account/Dimension Description Dr Cr 5103-007 Office Expense – Cost Center 700   5103-257 Office Expense – Department 300   5103 Office Expenses   1000 From the above ledger impact, the GL balance stays the same, but the amount gets distributed between the 2 dimensions in the exact proportion. II. Using advanced rules to assign an additional dimension to a particular GL account only. To understand this requirement, let’s take the example of an organization that has a mandatory Department dimension assigned on all expense accounts. But there may be an exceptional case where one expense GL account requires one more dimension apart from Department.   In this case, if we add a dimension in the account structure, then that dimension will be needlessly assigned to all GL accounts. We must ensure that it should be applicable to the one account only. For this, we use the concept of Advanced Rules. With the help of Advanced Rules, we can configure the Account Structures to accommodate any additional dimension for one particular GL account only. The steps to configure it are as follows: – Go to: General ledger -> Chart of Accounts -> Structures -> Advanced Rule Structures The screen displays all the Advanced Rule Structures present. Create a new one. Select the dimension that is required. In this example, we have selected the dimension of ‘Worker’ and kept it as mandatory. Activate the Advanced Rule Structure and close it. Open Account Structures. From the above image, all the GL accounts here will have a mandatory Department dimension. But let’s assume that one GL account – 4101 will require the dimension for Worker along with Department. For that, open Advanced Rules on top. Create a new rule. Select the Main Account where you want to apply the dimension as shown above. Then in the below section, add the Advanced Rule Structure that was created earlier. The rule works like this: – If Main Account = 4101, then apply Advanced Rule Structure where dimension = Employee. Therefore, in any transaction with the account 4101, it will assign the Worker dimension on it. Let’s take an example where a GL account other than 4101 is used here. In this transaction, for the account 4102, the system is prompting us to select the Department dimension only, as required. Now let’s select the account 4101. As observed from the above image, the system is now prompting us to select the Worker dimension also. Thus, this ensures that only some GL accounts may be configured to enter an additional dimension. We can also configure the rules such that there are combinations of Main Accounts and Dimensions to add any additional dimension. … Continue reading Distributing GL amounts between financial dimensions and using advanced rules to link a dimension to only one particular account →