Introduction Notifications in Business Central are alerts that appears in the Notification bar based on User actions. Notifications stack up from top to bottom, lasting until the user dismisses them, including those from sub-pages.  Validation errors are prioritized and shown before other notifications. We can use this to alert the user regarding something without taking all the user’s notification towards it, in the way messages or errors do. They also have the option to allow Users to make a corrective action by embedding the action button directly into the notification. Let’s see how it works. Source Code Pre-requisites Business Central OnPrem/Cloud. References Notification – Business Central Docs Configuration Here, for an example, I’ve created one simple page which takes two inputs. 1. The message that is to be shown in the notification. 2. The message to be shown after the User clicks on the action embedded in the notification. And I have two actions which I’ll be using to show/hide the notification itself. Both of those combined result in a page like below – Now, here is the list of procedures that are available with a “Notification” variable. Let us walk through these one by one. Message – Specifies the content of the notification that appears in the UI. The message function is what we use to decide what the notification will say.  I set up a global variable (Message) on my page so the user can type in a value directly, and that value will appear in the message. Scope – Specifies the scope in which the notification appears. According to Microsoft Docs, it is meant to specify the context in which the Notification appears. However for now, we only have the “Local Scope” available as an option so can’t comment much on this. Send – Sends the notification to be displayed by the client. Send is the function used to actually trigger the Notification in the UI. It returns a boolean value indicating whether the notification was triggered successfully or not. Set Data – Sets a data property value for the notification.Get Data – Gets a data property value from the notification.Has Data – Returns a boolean value indicating whether the notification has that value. These three functions work similar to a dictionaries Get, Set or Has functions. As Notifications can be used to perform actions, we need to store some data in them. This data is stored using key value pairs using the “Set Data” function. Then later we can retrieve it back using the “Get Data” function by passing in the specific key.  However, if the Key does not exist, we get a run-time error, thus we can use the “Has Data” function to check whether our notification has the specified key. Please note that the data in the Notification is stored till the User dismisses the notification or exits from the page. Add Action – Adds an action on the notification. Here, in the “Show Notification” action, I have added the “Set Data” function to store the data within the global variable “MyData” into the notification with a key as “MyData” as well. Then, we call the “Add Action” function the following parameters In the “Notification Action” codeunit i’ve created a simple procedure which checks, gets and then messages out the value set in the “MyData” key. And so, we get the following output when we click on the action button on the notification. When we click on the action button, the notification automatically disappears. Recall – Recalls a sent notification. However, if we want to manually recall a notification, we can use the “Recall” procedure. After I click the “Hide Notification” button. Id – Gets or Sets the GUID ID for an individual notification. We can use the ID function to Get to Set the ID for a particular notification. We can use this in conjunction with the other functions by passing the ID of one notification and using that to get the data from that notification instead of passing the Notification variable itself. Here I’ve made some changes to the “Show Notification” action such that now it pops up two notifications instead of one and I am storing the ID of the second notification. This is the output. Now, here is the “Hide Notification” action which will be using the ID saved from earlier to recall just the copy notification. And this is the output. Conclusion Thus, we saw how we can use notification to provide non-intrusive alerts to the User along with actions. Happy Coding!

We are delighted to announce that UAE based IT Professional Service Company is partnering with CloudFronts to deploy Sales to Invoicing with Dynamics 365 Project Operations and Power BI reporting.  The client leverages the best innovations in the cloud to help companies get ahead. The facilitated cloud integration solutions they provide are secure and combine advanced capabilities with technological ease, offering exceptional value to increase business efficiency. They help companies leverage Cloud, Mobility, AI, IoET and Big Data to serve their customers better and transform their businesses. Along with our client, their parent entity and 6 other legal entities are looking to implement Sales to Billing automation on Dynamics 365 to resolve issues around inefficient and siloed systems. This implementation will help carry out Sales, Project Management and Billing from a single platform and give insightful data through robust reporting capabilities.  The platform to be implemented is Dynamics 365 Project Operations with Power BI to carry out Sales to Project Management Operations. Applications like Outlook, SharePoint and Teams will also help optimize the platform’s use.  On this occasion, Priyesh Wagh, Dynamics 365 Practice Manager at CloudFronts, said, “We are thrilled to partner and get on this journey towards digital transformation. By leveraging Dynamics 365 Project Operations, we aim to streamline our client’s sales-to-invoicing process, enabling them to deliver exceptional services more efficiently.  About CloudFronts   CloudFronts is a Dynamics 365 focused Microsoft Solutions Partner helping Teams & Organizations worldwide solve their Complex Business Challenges with Microsoft Cloud. Our head office and robust delivery centre are based out of Mumbai, India, along with branch offices in Singapore & the U.S.  Since its inception in 2012, CloudFronts has successfully served over 500+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.   Please feel free to connect with us at transform@cloudfronts.com 

Introduction: Creating a tenant in Microsoft Entra-ID or Azure Active Directory (AAD) is a simple process that can be accomplished through the Azure portal. The portal serves as a centralized hub for managing Azure Active Directory and executing various administrative tasks, including the creation of a new tenant. Additionally, this blog will cover how to create a user and grant them permissions. Pre-requisites: Steps: Sign in to Azure Portal. Navigate to Microsoft Entra ID tenants: Select “Create”: Choose the type of tenant: On the Basics tab, select the type of tenant you want to create: Click Next: Configuration to proceed. Provide the necessary information: Organization name: Type your desired organization name (e.g., “Cloudfronts”). Initial domain name: Choose an initial domain name (e.g., “cfblogs”). Country/Region: Select your desired country or leave it as the United States. Review and create: Your new tenant is created: Check your user account: User can change their User Principal Name (which is generated by the system) by clicking on user e.g. “Shubham Prajapati” Now Sign in to Business Central Business Central Sign In | Microsoft Dynamics 365 Now put the User principal name As password was not set during tenant creation. Go to > Forgot Password After setting up the password you can successfully login to your Business Central Now Go to Settings > Admin Center Now Click on Upper Left Corner > Admin Go to Active Users > Click on the user which you want to give permission to access central, then go to Licenses and apps and select Licenses > Save changes Once permission is provided Go to Users page in business central and click on Update users from Microsoft Now the user is being updated, to give environment permission click on the user whom you want to give permission To give environment permission to user click on New Line > Select appropriate permission to user Conclusion Thus, in this blog we saw how to create a tenant for business central and how to add users and give permissions to them. Thank you for reading hope this helps!

We are delighted to announce that the largest US-based casting manufacturer is partnering with CloudFronts for Dynamics 365 support & maintenance with a Managed Services Agreement (MSA).  The manufacturer and distributor based in Houston, Texas, is doing business since 1960 with facilities in the United States, India, and China. It was one of the first innovators to globally source municipal castings and utility fittings in the United States. They have set the standard for quality and reliable globally sourced products in an economical manner for the utility marketplace and OEM castings. Under this MSA, CloudFronts will provide support & maintenance services for the system based on Microsoft Dynamics 365 Sales.  On this occasion, Priyesh Wagh, Dynamics 365 Practice Manager at CloudFronts, said, “We are delighted to collaborate and support the client’s business objectives through our Managed Services Agreement. This partnership underscores our commitment to delivering unparalleled support and innovative solutions to help our client achieve its business goals effectively.”  Visit us at https://www.cloudfronts.com/ to learn more about our Dynamics 365 offering  About CloudFronts   CloudFronts is a Dynamics 365 focused Microsoft Solutions Partner helping Teams & Organizations worldwide solve their Complex Business Challenges with Microsoft Cloud. Our head office and robust delivery centre are based out of Mumbai, India, along with branch offices in Singapore & the U.S.  Since its inception in 2012, CloudFronts has successfully served over 500+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.   Please feel free to connect with us at transform@cloudfronts.com 

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!

HECO-Pacific Manufacturing has partnered with CloudFronts to implement Dynamics 365 Business Central. With this collaboration, HECO-Pacific Manufacturing continues its goal to use innovative technology to improve productivity and streamline business procedures.  HECO Pacific has been in business since 1961 providing all types of material handling equipment. They have built some of the most complicated cranes in the industry for some of the toughest customers. This experience has also allowed them to provide a wide range of standard cranes for light duty applications. Learn more about them at http://www.hecopacific.com/  HECO Pacific is looking to migrate from QuickBooks to Dynamics 365 Business Central to improve existing processes and bring efficiency to the organization. Some of the key objectives of this project are to automate reconciliation, manage the entire life cycle of the procure to pay and order to cash cycles in the platform, improve reporting for actions (like PO with due dates), approval processes and finally leverage this new platform for further automation in the future like time entry using project line barcoding.  On this occasion, Jimil Bhatt, Dynamics 365 ERP Team Lead at CloudFronts, said, “We are excited to partner with HECO-Pacific Manufacturing on their journey towards digital transformation. Dynamics 365 Business Central is an ideal solution for Heco Pacific, and we look forward to ensuring they achieve their goals efficiently.”  About CloudFronts   CloudFronts is a Dynamics 365 focused Microsoft Solutions Partner helping Teams & Organizations worldwide solve their Complex Business Challenges with Microsoft Cloud. Our head office and robust delivery centre are based out of Mumbai, India, along with branch offices in Singapore & the U.S.  Since its inception in 2012, CloudFronts has successfully served over 500+ small and medium-sized clients all over the world, such as North America, Europe, Australia, MENA, Maldives & India, with diverse experiences in sectors ranging from Professional Services, Financial Services, Manufacturing, Retail, Logistics/SCM, and Non-profits.   Please feel free to connect with us at transform@cloudfronts.com 

Introduction: A Step-by-Step Guide to Creating Opportunities and Processing Sales in Business Central Pre-requisites for creating Sales Opportunities: Create Sales Opportunities You can create opportunities from the Opportunity List page. Typically opportunities are created from a specific contact or salespeople. Globally search “Salesperson” and select related link. Select the salesperson from the list for whom you want to create an opportunity. On the salespeople card page, select opportunities action –> selected salesperson opportunities page will open up –> user can create new by clicking on New action. If opportunity is created through salespeople then salesperson code is automatically generated. Globally search “Contact” and select related link. Contacts list page will open up, user can select the contact for which opportunity has to be created. Click on Home –>Create Opportunity for new opportunity. Click on Contact–> Open Opportunity (To view existing opportunity of selected contact) If opportunity is created through contact then contact name is automatically generated. No. – This field is auto generated based on the set no. series. Description – Description of the opportunity. Contact no. – User can select existing contact or create new. Contact name: Contact name is auto generated based on contact no. Phone/mobile/email: Auto generated from contact card page. Contact company name: This field is auto generated from contact card page Salesperson code: if opportunity is created through salesperson then this field is auto populated, if not then user can manually select the salesperson. Campaign no. User can select specific campaign to link with the opportunity. Priority: The default priority is set as normal. Other priorities are Low and High. Sales Cycle code: This is a setup. (To know more refer part 1 of this blog) Status: The status field is updating automatically. Closed: Specifies if the opportunity is closed. Creation date: Opportunity creation date  Date Closed: Specify the date the opportunity was closed. Segment no.: User can link segment to the opportunity. (If any) Sales cycle stages To start the sales cycle, user can click on “Activate first stage” To move an opportunity through sales cycle stages: Sales cycle stage is automatically updated Fill in the rest of the details as necessary. To Close opportunity When the negotiations are finished, you can close the opportunity. When closing an opportunity, you can specify whether it was won or lost, as well as why it was closed. To specify a reason, you must set up closed opportunity codes. To Create Sales Quote To Create Sales Order To Delete Opportunities After you have deleted an opportunity, it is removed it from the Opportunity List page. Conclusion Microsoft Dynamics 365 Business Central provides a robust framework for creating opportunities and processing sales seamlessly. By following this step-by-step guide, you can harness the full potential of Business Central to optimize your sales processes, enhance customer relationships, and drive business growth. Hope this helps!