Inc. 5000 Fastest-Growing Company in the US

inc-5000-logo
Ascent Innovations Logo
Schedule
by
What is Safety Stock?

What is Safety Stock? Table of Contents What is Safety Stock? Safety stock or buffer stock is the additional quantity of an item above the desired quantity that is held in the on-hand inventory. Such extra inventory is held with the sole purpose of avoiding the risk of running out of stock. Safety stock serves as an insurance or a cushion for manufacturers and retailers against possible out of stock situations for an item. Such stock outs are caused usually by: Changes in the demand for the item Inaccuracies in the forecasts of the item Unforeseen disruption to the supply line of the item Maintaining safety stock for an item comes with its own challenges. The first is the identification of the appropriate method of calculation in arriving at the right quantities that need to be maintained for each item. The second is the increase in the working capital to store additional on-hand quantities. So, the right safety stock for an item should strike a balance between the conflicting goals of maximizing customer experience (satisfaction) and the cost of managing additional inventories. Why to maintain Safety stock? The important reasons to maintain the safety stock is to prevent the business from stock out situations which arise due to various internal and external factors. Some of the major factors are: External Factors: Fluctuation in demand: A spike in consumer demand often results in stock outs. Spikes in consumer demand can be attributed to many reasons including festivals, seasonal and any act of nature (epidemic). Variation in supply line: Any disruption to the supply line by the vendor leads to stock outs. It might be due unforeseen reasons including weather-related shipping delays, and vendor’s production bottlenecks. Internal Factors: Inaccurate Forecasts: Any inaccuracies in the forecasts lead to stock outs. Such inaccuracies might be due to the nature of the product itself, or lack of accurate data and lack of proper tools and techniques. Production delays: Any unexpected delays in the production and transportation in the internal value chain lead to stock outs. It might be due to unexpected breakdowns in the production line and industrial unrest. Variation in consumer demand is the single major reason for the maintenance of safety stocks. Stock outs are undesirable as they adversely affect the business. Some of the major impacts to business are: Loss of Sale: In the highly competitive marketplace, it is quite tough to regain a lost sale, and often declared as the ‘lost opportunity’. Erosion of Market Share: Poor service delivery due to stock out starts with the erosion of customer base and ends with the erosion of market share. Strained Supply chain: Stock out puts additional burden on the supply chain, and it strains the relationship between partners of supply chain. The advantages of maintaining safety stock levels Holding sufficient levels of safety stock reduces the risk to stock out and there by provides the business the following insurance cover: Prevents stock out due to sudden spikes in consumer demands Prevents stock out due to uncertain lead times of vendors and internal production line Prevents stock out due to disruption to the supply line from vendors Prevents stock out due to inaccurate forecast Ensures customer service and satisfaction levels Ensures continued sales and market share Helps to maintain healthy relationship with supply chain partners Helps to automate the reorder points How to employ Safety stock in the supply chain? Though the purpose of maintaining safety stock is to avoid stock outs, it is not intended for all stock outs but for majority of them. While calculating the safety stock levels a right balance should be arrived between the opposing objectives of satisfying customer requirements at a specific service level and the cost of holding additional inventory. Since not all items are same, any general application of safety stock policy has adverse effects.   Some organizations often employ the policy of using their rule of thumb to arrive at the safety stock levels in the absence of any modern automation tool or software under their disposal. Such policies often end up with more disturbances to business than the expected improvement.   A robust inventory management system supported by a dynamic planning engine is required for business to handle the safety stock level and to process automate item replenishments. A statistical calculation technique is required for business to manage the conflicting goals of maximizing customer experience and the cost of managing the additional inventories. Microsoft Dynamics 365 offers a robust and scalable supply chain solution to manufacturers and retailers with end-to-end supply chain and inventory management processes, including the safety stock management, and seamlessly integrated with the modules of Finance, Purchase and Master Planning for accounting, replenishment and reporting. Solution offered by D365 Finance & Supply Chain (or Operations) Safety stock level fulfills the following purposes:   1. Act as the buffer stock against to prevent stock out scenarios   2. Act as a demand (reorder point) thereby triggering the automatic fulfillment ordersWhile safety stock levels prevent stock outs, it also serves as the reorder point or act as a system generated demand, where automatic replenishment policies can plan for item coverage for a given period. Thus, safety stock offers the process automation and reduces human efforts in managing the desired stock levels. As part of item replenishment policy, safety stocks are configured for items according to their consumption and importance to business. With a clear marking of safety stocks for items, master planning engine takes care of replenishment based on the (Coverage plan) policies attached to the item.   Management of safety stocks in D365 F&O requires knowledge about 3 different aspects of safety stock. Configuration required for using safety stock Automatic replenishment policies Recalculation of safety stock levels Configuration and automatic replenishment policies The configuration and automatic replenishment policies for safety stock cover the following: What to plan? Where to plan? When to plan? How to plan? What to plan: The fundamental and one of the important set up for safety stock is the setup of the coverage plan (replenishment … Read more

by
D365 Business Central: Because Guesswork is Not a Strategy

D365 Business Central: Because Guesswork is Not a Strategy Table of Contents D365 Business Central: Because Guesswork is Not a Strategy Running a business without an integrated system is like driving with a foggy windshield—you can sort of see where you’re going, but it’s mostly guesswork, and you’ll probably hit something eventually.   That’s why Microsoft Dynamics 365 Business Central exists. It clears up the view by giving companies real-time visibility into finance, inventory, and operations—without bogging people down with features they don’t need. Making Decisions Without Second-Guessing Most decisions are made with some combination of spreadsheets, gut instincts, and “we’ve always done it this way” logic. Sometimes it works. Other times, it’s a costly mistake that everyone pretends never happened.   Business Central fixes this by centralizing financials, supply chain oversight, and business analytics into one system. No more process gaps. No more reporting blind spots. Just accurate, up-to-date information that actually tells you what’s happening across the company.   So when a manager asks, “Where’s that report?”, the answer isn’t “I’ll check with accounting” (which we all know means “You won’t see it for three days”). Instead, the numbers are already there—live, in real time, ready for decision-making. Why Business Central Works at Every Level For Executives: Clarity on What Is Really Happening Everyone wants to make data-driven decisions, but that’s hard to do when the data is scattered across five different systems, three spreadsheets, and one email thread.   With Business Central, everything is integrated. Financials, sales, supply chain, and operations are all in sync, so leaders can actually see what’s working (and what’s not) before it becomes a problem. What this means in practice: Cross-functional teams solve problems faster because they’re working from the same information. No more “firefighting” meetings because the system flags issues before they become crises. Accountability becomes real since reports are trusted to be accurate, everyone takes ownership, and the results are a team effort. For Departments: The Time and the Facts for Collaboration Every functional team is locked in a daily battle to keep things moving. Finance is reconciling numbers, chasing discrepancies, and making sure cash flow isn’t a guessing game. Sales is focused on closing deals, often making promises based on a hallway chat rather than data. Operations is managing fulfillment, dealing with unexpected delays, and constantly adjusting schedules. Supply chain is pushing orders through while hoping inventory holds up. Each team is winning the day, but only by fighting fires as they come—which burns out your people and limits growth. With so much time spent figuring out what’s happening and reacting to problems, there’s little room for deeper analysis—let alone collaboration with peers. Teams want to work smarter, but rarely have the breathing room to step back and see the bigger picture. Business Central fixes this. Lead-to-order and order-to-cash processes are fully streamlined, meaning sales, finance, and fulfillment all see the same data at the same time. The S&OP process actually works because teams can track performance metrics in real time, not in outdated spreadsheets, to improve planning and execution. Automation eliminates manual tasks, freeing your best people from admin work so they can analyze real-time trends, solve problems faster, and make adjustments before it’s too late to change results. Adjustments can be made before problems spiral since teams can monitor real-time result, instead of playing catch-up days or weeks late. For Finance: Finally, a System That Makes Sense Finance teams love numbers. But they don’t love chasing them across disconnected systems. Business Central simplifies Financial Planning & Analysis (FP&A) by providing a single view into daily sales, operational, and financial performance. This means: Real-time financial data, eliminating the wait for someone to “run the numbers.” Better forecasting and budgeting, as the system helps predict trends instead of relying on historical guesswork. Fewer surprises, since KPIs that drive sales, operating margin, and cash flow are visible at all times. For Supply Chain & Inventory Management: A Scoreboard for Success Stock-outs disappoint customers and create backlog, slowing the cash conversion cycle. If inventory management is a sport, most businesses are playing without a scoreboard—lots of action, constant movement, but no clear way to track what’s working or where they need to adjust to win for both the customer and the company. Business Central fixes this with: Inventory valuation tracking, supporting FIFO, LIFO, and average costing—configured for accuracy. Automated replenishment, allowing businesses to set reorder points and let the system handle purchase orders. Warehouse efficiency tools, including bin tracking, shipment tracking, and streamlined receiving processes to keep inventory moving smoothly. ERP Right-Sized for SMB D365 Business Central isn’t for massive enterprises with infinite IT resources—it’s for companies that need real control over finance, inventory, and operations without getting bogged down in complexity.   So, if you’re tired of making business decisions based on outdated reports, best guesses, or sheer optimism, it might be time to take a serious look at D365 Business Central. About the Author Balaji Sekar has spent 18 years configuring, customizing, and making ERP systems actually work. As a Microsoft Dynamics 365 consultant, he helps manufacturing companies ditch manual processes and embrace automation in D365 Finance and Supply Chain and D365 Business Central. With deep expertise in cross-functional business process design, he knows firsthand that the real challenge isn’t just implementing a system—it’s about getting the details right the first time. Balaji Sekar Microsoft Dynamics 365 consultant Latest Posts You might also like:

by
Committing to Accurate Barcodes: Because Royal Doulton Looks Weird Next to a Sippy Cup

Committing to Accurate Barcodes: Because Royal Doulton Looks Weird Next to a Sippy Cup Table of Contents Share Committing to Accurate Barcodes: Because Royal Doulton Looks Weird Next to a Sippy Cup Take a moment and think about the most exciting and joyful moment of your wedding. If you aren’t married, then try to imagine it. What did you pick? The expression of your love and faithfulness to your spouse? While that’s a sweet sentiment, you’re wrong.   Throwing a party for your family and friends? Barring the judgmental looks from Great-Aunt Ethel, sure, that’s fun. However, the price can sap away some of the enjoyment. So, no. Still wrong.   What about the cake? Surely something so simple, honest and delicious has to be the right answer. Nice try, but still no.   No, the most exciting and joyful moment of your entire wedding is setting up a wedding registry and walking around the store with a scanner. You get to pick all the things you like, decide in that moment you are absolutely going to host weekly candlelight suppers for 12 guests, and shoot laser beams out of a handheld device.   The entire experience hinges on two very important principles: Commitment and Accuracy. If you and your spouse aren’t in love with the Royal Doulton with the hand-painted periwinkles, then you might be stuck with that pattern for a long time. Likewise, if you want twelve place settings and find out much later the store doesn’t quite have twelve of everything, then one of your guests is going to have an awkward dining experience. Similarly, a successful inventory barcode process heavily relies on commitment and accuracy to ensure a dependable and long-lasting implementation within your organization. Commitment On the surface, one might think that developing an inventory barcode process is pretty simple. Take some key data, translate it into a barcode or QR code, print it on a label and slap it on the box. Done. However, a barcode label is a commitment to a static set of parameters and a narrow interpretation of that data. Let’s take some typically requested fields and put them into context. Logo: Putting the company logo or name on a product label is very common. However, think of the potential ramifications once that package leaves your dock. Do you have customers that demand private labelling? That logo is going to lead to some angry phone calls. Does the competition have access to your client’s facilities or inventory? Don’t make it easy for them to cross-reference your product. Space: Once you have committed to a certain label size, make sure all the fields are tested. If one line on the label can only fit 45 characters but the form field has a 60-character limit, you risk wrapping to the next line and most barcode scanners cannot read that information. Even worse, the extra characters may get cut-off entirely leaving incomplete data and a non-readable barcode. Description: This is a helpful field. While an item number means something to procurement, it might be useless to a warehouse worker. The description should very clearly indicate what the item is. That said, does it really need a barcode? Perhaps that extra space could be utilized elsewhere. Date: A date is good, especially for items with a shelf-life. Which date do we use? Purchase date? Receipt date? Label print date? This should be clearly indicated on the label. Remember, we want to leave as little open to interpretation as possible. Alternatively, consider relying on batch and/or serial numbers, as that data can be easily traced to the originating documents and journals. Quantity: This is commonly requested and very tricky. Let’s assume we’re receiving one box of twelve tubes of sealant. As long as we always commit an entire box in our sales or production process, there’s no issue. However, as soon as we remove one tube from that box, our label is incorrect and that can lead to serious inventory issues and the segue to our next topic. Accuracy Simply put, bad data is asking for trouble. Printing a barcode and placing it on a box is capturing a moment in time. Once any of the variables change, the label is no longer accurate. If the label is inaccurate, then it’s only a matter of time before your physical inventory no longer matches your database inventory. Timing: When are labels reprinted? Assuming the original label is printed upon product receipt, when, if ever, is an updated label generated? If we remove certain fields such as quantity or date, we can avoid bad reporting. Reprint Functionality: If a label is to be reprinted, what is the process? A warehouse worker may think they are being helpful by reprinting a missing label. However, if they assume the serial or item number, we may have a serious problem. There needs to be a safeguard in the business process or at the label generation point to ensure the correct data is printed. Warehouse Dimensions: While it may seem like a good idea to print the item’s location at receipt, that data can become problematic after the fact. Let’s say the inventory was received into Bin 1 but was moved via transfer journal to Bin 2 for space optimization. Without reprinting the label, a worker may think he found an item in the wrong location and move it back. Special Characters: Ampersands, slashes and hyphens are great for shortening and delineating descriptions but they can wreak havoc on a barcode. If the scanner cannot read special characters, then have them removed from the barcode programmatically or consider reformatting the form field. When developing a barcode label, the most important thing to remember is that data is dynamic and labels are static. As managers and consultants, our goal is to make a user’s job as easy and foolproof as possible. Labels can help, but they can hinder as well. Inaccurate inventory counts, loose reprint procedures and poor formatting can lead to questions which then lead to assumptions and inefficiencies. … Read more

by
Microsoft Cloud for Manufacturing

Microsoft Cloud for Manufacturing Table of Contents Modern Manufacturing What Is Microsoft Cloud for Manufacturing? Microsoft Cloud for Manufacturing is a cloud-based solution designed specifically for manufacturers, helping them become more agile, efficient, and resilient. It brings together powerful tools like Azure, Dynamics 365, Microsoft 365, Microsoft Teams, and Power Platform to create a connected, intelligent manufacturing ecosystem.   With built-in AI, IoT, and automation capabilities, manufacturers can get real-time insights, streamline operations, and proactively manage risks—helping them stay ahead in a rapidly changing industry. Key Capabilities of Microsoft Cloud for Manufacturing 1. Strengthening the Supply Chain Supply chain disruptions and unpredictable demand can create major challenges for manufacturers. Microsoft Cloud for Manufacturing helps businesses gain visibility, plan smarter, and reduce risks. Real-time supply chain visibility – Use AI-powered insights in Dynamics 365 Supply Chain Management to monitor supplier performance and identify risks before they become problems. Better demand forecasting – Improve planning with AI-driven models that predict demand trends, helping manufacturers balance supply and demand more effectively. Warehouse & fulfillment optimization – Streamline inventory tracking, warehouse operations, and order fulfillment to reduce delays and costs. 2. Improving Production & Quality Keeping production efficient and maintaining high quality are critical for success. Microsoft Cloud for Manufacturing gives manufacturers real-time insights and automation tools to improve output and reduce waste. Production monitoring & optimization – Track factory operations in real-time and use AI-driven analytics to optimize processes and reduce downtime. Automated quality control – Leverage AI-powered inspections and real-time tracking to ensure product quality and reduce defects. Digital twins & simulation – Simulate production changes before implementing them, allowing for smarter decision-making and improved efficiency. Empowering Workers with Smart Tools Modern manufacturing requires a connected workforce with access to the right information at the right time. Microsoft Cloud for Manufacturing provides tools that help employees work smarter. Connected workers – Use Microsoft Teams, Power Apps, and HoloLens 2 to improve collaboration, training, and productivity on the factory floor. Hands-free assistance & training – Enable employees to receive remote guidance and training through augmented reality tools like Dynamics 365 Guides. Enhancing Customer & Field Service Customers expect fast response times and proactive service. Microsoft Cloud for Manufacturing helps manufacturers improve engagement and service quality. Preventative field service – Use AI and IoT to predict equipment failures before they happen, reducing downtime and improving customer satisfaction. Stronger B2B customer engagement – Build better relationships with customers using AI-driven sales, marketing, and customer insights tools. What’s Next? Microsoft’s Continued Investment in Manufacturing Microsoft is constantly adding new features to help manufacturers stay competitive. Some of the latest innovations include: AI-powered summaries – Quickly generate concise summaries of manufacturing data using AI, making it easier to find key insights. Faster portal creation – Build customer and partner portals using AI-driven natural language tools, reducing development time. Autonomous AI assistants – Improve customer support with AI-driven virtual agents that interact with users in real time. Stronger cybersecurity & compliance – Enhanced authentication and security features to protect sensitive data. Why Ascent Innovations? With 16 years of experience in Microsoft ERP, analytics, and digital transformation, Ascent Innovations helps manufacturers get the most out of Microsoft Cloud for Manufacturing. Implement AI-powered manufacturing solutions for supply chain, production, and field operations. Connect Microsoft Power Platform, Azure, and Dynamics 365 to streamline processes and improve decision-making. Use real-time analytics to improve forecasting, efficiency, and business performance. Strengthen customer engagement, security, and compliance to future-proof operations. Take Your Manufacturing to the Next Level The future of manufacturing is all about agility, intelligence, and automation. Microsoft Cloud for Manufacturing provides the tools you need to compete today while preparing for tomorrow.   Want to get started? Contact Ascent Innovations to learn how we can help you maximize your investment in Microsoft Cloud for Manufacturing. About the Author Abdul Hafiz is a business and technology strategist with 25+ years of experience in optimizing and implementing ERPs to modernize finance and operations. As a Partner at Ascent Innovations, he has led growth and delivery for 14 years. He holds a master’s degree in computer and information sciences from the University of Illinois and advises executive teams on how to modernize the enterprise to drive profitable growth. Author: Abdul Hafiz Enterprise Solution Architect Icon-linkedin Latest Posts You might also like:

by
Replaceable Attributes in D365 Operations

Replaceable Attributes in D365 Operations Table of Contents Share Replaceable Attributes in D365 Operations We were working for an extension modelling in Dynamics 365 for Operations in standard Bank module. The standard process is to download the “Bank Positive Pay” file information, which will be downloaded as text file. Standard business scenario We were working for an extension modelling in Dynamics 365 for Operations in standard Bank module. The standard process is to download the “Bank Positive Pay” file information, which will be downloaded as text file. Change Request The approach was to avoid this manual process and automate the bank Positive Pay process. We bypassed the standard downloading process and instead transferred these positive pay files into Azure BLOB storage automatically. Then from Azure BLOB storage, an external web service will pick these files for automatic payment processing, usually an FTP service which works for most banks. Figure 1. Data Management in Dynamics 365 for Finance and Operations The reasons include the business policies on data security and operational efficiency. The reasons could differ based on business cases, however the focus here is on the programming aspect. Analysis If you further examine the arrangement of the code to deliver the file, the standard code downloads the file. (Classes/BankPositivePayExport/sendFileToDestination) /// <summary> /// Send file to destination. /// </summary> [Replaceable] protectedvoid sendFileToDestination() { str downloadUrl = DMFDataPopulation::getAzureBlobReadUrl(str2Guid(fileId)); Filename filename = strFmt(‘%1-%2%3′, bankPositivePayTable.PayFormat, bankPositivePayTable.PositivePayNum, this.getFileExtensionFromURL(downloadUrl)); System.IO.Stream stream = File::UseFileFromURL(downloadUrl); File::SendFileToUser(stream, filename); } As per Chain of Command (or Event Handlers), we have option to only write custom code either before method execution or after method execution. But in this case since standard method was already downloading file. Challenge here was to see how we can block or bypass the standard code.   Since NEXT command is mandatory in calling Chain of Command method, when this NEXT command is called standard code will get executed and file will be downloaded to the local computer. <Chain of command> Pre code NEXT () <standard code of sending positive pay>Mandatory Post code <End of Chain of command> Resolution About Replaceable Attributes With replaceable method, we need not call NEXT command in Chain of Command (CoC) and completely override the logic written by standard Microsoft code. But Microsoft suggests using this NEXT command conditionally.   As part of this blog, let’s see how to mitigate the scenario of blocking the standard local file storage and get the file stored in Azure BLOB’s. Create an extension class for “Classes/BankPostivePayExport” usingMicrosoft.WindowsAzure.Storage; using Microsoft.WindowsAzure.Storage.Blob; [ExtensionOf(classStr(BankPositivePayExport))] finalclass BankPositivePayExport_Extension { } By replaceable attribute, write code to store in Azure BLOB This method is actual replaceable method in “Classes/BankPostivePayExport”. Following code explains how we wrote custom logic to download the file and send it for Azure BLOB storage. /// <summary> /// Sends file to Blob storage /// </summary> protectedvoid sendFileToDestination() { #define.Underscore(“_”) #define.DOT(“.”) #define.XML(“XML”) #define.FILENAME(“ASCPositivePay”) if (this.parmBankPositivePayNum()) { BankPositivePayTableascbankPositivePayTable; ascbankPositivePayTable= BankPositivePayTable::find(this.parmPostitivePayNum()); ASCDownloadURL downloadURL; ascDownloadURL = DMFDataPopulation::getAzureBlobReadUrl(str2Guid(fileId)); Filename filename = strFmt(’%1%2%3%4%5’, #FILENAME, ascbankPositivePayTable.PositivePayNum, #Underscore, System.String::Format(’{0:MM.dd.yy}’, today()), #DOT + #XML); System.IO.Stream stream = File::UseFileFromURL(downloadUrl); CloudBlobContainer blobContainer; blobContainer = this.connectToBlob(“<Name from Azure Key vault>”, “<Key from Azure Key Value>”, “<BLOB Folder name>”); this.uploadFile(blobContainer, stream, filename); } } Establish connect to Azure BLOB container Following code establishes the connection with Azure BLOB. As a safety measure directly storage account name, account key and container name is not advisable, these values should be stored in Azure Key Vault and picked based on tokens (Note: Concept of storing and retrieving from key vault is outside scope of this blog, you can refer to Azure Key Vault article on how to store and retrieve storage keys) /// <summary> /// Establish connection to blob storage /// </summary> /// <param name = “_storageAccountName”>Storage account name</param> /// <param name = “_accountKey”>Account key</param> /// <param name = “_blobContainerName”>Blob container name</param> /// <returns>Blob container</returns> public CloudBlobContainer connectToBlob(ASCStorageAccount _storageAccountName, ASCAccountKey _accountKey, ASCBLOBContainer _blobContainerName) { CloudBlobClient blobClient; CloudBlobContainer blobContainer; CloudStorageAccount storageAccount; ASCConnectionString connectionString; connectionString = strfmt(@ASC:ConnectionString, _storageAccountName, _accountKey); storageAccount = CloudStorageAccount::Parse(connectionString); blobClient = storageAccount.CreateCloudBlobClient(); blobContainer = blobClient.GetContainerReference(_blobContainerName); return blobContainer; } Labels @ASC:ConnectionString= ”DefaultEndpointsProtocol=https;AccountName=%1;AccountKey=%2;EndpointSuffix=core.windows.net” Custom method to upload file to Azure BLOB This is a custom method, which explains how the BLOB container is uploaded to Azure BLOB. This method takes file stream, blob container name and blob file name as input to create files in Azure BLOB. /// <summary> /// Uploads the file to the blob /// </summary> /// <param name = “_blobContainer”>Blob container</param> /// <param name = “_stream”>File stream</param> /// <param name = “_fileName”>File name</param> publicvoid uploadFile(CloudBlobContainer_blobContainer, System.IO.Stream_stream, FileName_fileName) { _blobContainer.CreateIfNotExistsAsync(); try { ttsbegin; CloudBlockBlob blockblob =blobContainer.GetBlockBlobReference(_fileName); if(blockblob && !blockblob.Exists(null, null)) { if(_stream) { blockblob.UploadFromStreamAsync(_stream).Wait(); blockBlob.FetchAttributes(null,null,null); BlobProperties BlobProperties = blockblob.Properties; if(BlobProperties.Length == _stream.Length) { info(strFmt(“@ASC:FileUploadedSuccessfully”, _fileName)); } } } else { info(strFmt(“@ASC:FileAlreadyExists”, _fileName)); } ttscommit; } catch { info(“@ASC:ErrorUploadingFile”); } } Labels @ASC:ErrorUploadingFile =“Error while uploading file” @ASC:FileAlreadyExists =“File already exists” @ASC:FileUploadedSuccessfully=“File uploaded successfully” Conclusion We find this Replaceable Attribute cool and very beneficial in blocking the standard code completely and writing our own custom code. To know more about Do’s and Don’t’s of using replaceable methods, refer to the Microsoft documentation:   https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/extensibility-attributes#replaceable   This blog focuses on the ability to customize a standard behavior. However, we recommend to thoroughly evaluate the need to customize. Author: Krish Moorthy Technical Specialist – Microsoft Dynamics 365 Share Latest Posts You might also like:

by
From Cozy Coupe to the Real Deal: Why Training is the Key to Success

From Cozy Coupe to the Real Deal: Why Training is the Key to Success Table of Contents Share From Cozy Coupe to the Real Deal: Why Training is the Key to Success Twenty-five years ago, almost to the day, I was the picture of pure excitement. It was my 15th birthday, and I was standing in line at the DMV, ready to get my driver’s permit. After years of studying car magazines, playing with Matchbox cars, and perfecting my laps around the house in my Cozy Coupe, I was convinced I was ready. I couldn’t wait to slide behind the wheel of the family’s 1998 Saturn SL2, pop in my Discman-to-tape-deck converter, and blast Led Zeppelin. Best of all, in my fantasy world, the state of Illinois and my parents would recognize my extensive “training” and let me skip driver’s ed entirely. Unfortunately, despite my best efforts—including a PowerPoint presentation decked out in dazzling WordArt—there was no getting around the most critical part of learning to drive: actual training. The same logic applies to enterprise-wide software systems like ERP and CRM systems. No one in their right mind would toss a teenager the keys to a car without lessons, yet many organizations hand over a brand-new system without providing real training. What looks easy from the passenger seat can be overwhelming and dangerous when you’re in the driver’s seat. The Classic Excuses We’ve all heard them. Maybe we’ve even said them: “They’ll figure it out once they play around with it.” “Just send a write-up with some screenshots.” “We’ll hold a quick Teams meeting and call it a day.” This kind of thinking is short-sighted and, frankly, a disaster waiting to happen. Training isn’t just a checkbox—it’s an opportunity to ensure a successful implementation. Skimping on it is like skipping driver’s ed and expecting no one to crash. Why Intensive Training is Non-Negotiable? 1. Preparation The last thing management or a VAR wants on go-live day is a room full of people standing around in a panic. Training helps users get familiar with the system, understand processes, and recognize why certain decisions and features were implemented. 2. Buy-In Most users are skeptical of any system upgrade. “Everything was working fine before—why do we need this?” Training is the time to turn skepticism into excitement by showing users how the new system will actually make their lives easier. 3. Collaboration System upgrades often feel like marching orders from the C-suite, which can create resistance. But training turns the transition into a shared effort. When employees feel involved, the upgrade becomes a team-building opportunity instead of a source of frustration. 4. Reprieve A well-trained team reduces the burden on both management and the VAR. When multiple employees understand the system, they become in-house resources, making troubleshooting and ongoing training much easier. 5. Course Correction Hands-on training gives decision-makers direct access to the people who actually use the system. These frontline users often catch potential issues, risks, and areas for improvement—something that, of course, was totally covered in the pre-project surveys and documentation. (Right?) Building an Effective Training Approach There’s no one-size-fits-all method for training because corporate cultures vary. What works for a small industrial manufacturer won’t necessarily work for a multinational chemical company. That said, the most effective strategy I’ve seen (outside of the training method I once tried to sell before the state of Illinois shut me down) is getting on the floor with the users: Get to know them. Become someone they can approach without fear of reprimand or embarrassment. Explain why the system is changing—not just how. Walk through real-life examples. Listen to their concerns and answer their questions (seriously, don’t flake on this). And for the love of all that is good, be encouraging! If a user figures out a process on their own or explains a workflow correctly, celebrate it. That kind of enthusiasm spreads, and before you know it, the whole organization is engaged. Training is the Key to Success A well-managed, comprehensive training program will make or break a system implementation. When users are empowered and the “because management said so” barrier is removed, companies build stronger systems, foster collaboration, and turn employees into system experts. Plus, leadership and the implementation partner gain a more proactive, informed workforce, making go-live far smoother. So don’t just toss the keys to your team and act surprised when someone crashes through a chain-link fence. Train them first. About the Author Matthew Newcomb is an experienced and certified Microsoft Dynamics AX & 365 Supply Chain Functional Consultant, specializes in Advanced Warehousing and Production, who’s been navigating the twists and turns of ERP implementations long enough to know that training makes all the difference. As a functional solution architect, business analyst, and project wrangler, he helps companies get the most out of their Microsoft Dynamics solutions—without the headaches. When not untangling digital roadmaps, you might find Matt getting the Led out.   Author: Matthew Newcomb Senior Solution Consultant Icon-linkedin Share Latest Posts You might also like:

by
Migrate EWS Apps to Microsoft Graph for Exchange Online in D365 Finance and Operations

Migrate EWS Apps to Microsoft Graph for Exchange Online in D365 Finance and Operations Table of Contents Share Migrate EWS Apps to Microsoft Graph for Exchange Online in D365 Finance and Operations Exchange Web Services (EWS) is a legacy protocol that has been in use since Exchange Server 2007. In August 2018, Microsoft announced that there won’t be any active investment in EWS APIs for Exchange Online. We recommend that you migrate your EWS apps that access Exchange Online to Microsoft Graph. Checkout the below recording on how to set this up in D365 Finance and Operations. The exchange email provider stopped sending emails as of September 15, 2024. https://www.ascent365.com/wp-content/uploads/2025/03/Switch-from-Exchange-to-Microsoft-Graph-for-email-settings.mp4 Author: Sohena Hafiz President Icon-linkedin Share Latest Posts You might also like:

by
Why upgrade from Dynamics AX to Dynamics 365 Finance and Operations?

Why upgrade from Dynamics AX to Dynamics 365 Finance and Operations? Table of Contents Why upgrade from AX to Dynamics 365 Finance and Operations? Dynamics AX is a popular enterprise resource planning (ERP) software that has been widely used by businesses for several years. However, Microsoft has now released a newer version of the software called Dynamics 365 Finance and Operations, which offers many improvements and advantages over Dynamics AX. Here are some reasons why it’s time to upgrade from Dynamics AX to Dynamics 365 Finance and Operations:   1. Cloud-based Solution: Dynamics 365 Finance and Operations is a cloud-based solution that provides greater flexibility, scalability, and accessibility. With cloud-based solutions, you don’t have to worry about maintaining and updating on-premises hardware and software.   2. Improved User Interface: Dynamics 365 Finance and Operations has a modern and intuitive user interface that is easy to use and navigate. This can improve user productivity and reduce training time.   3. Advanced Reporting and Analytics: Dynamics 365 Finance and Operations comes with built-in reporting and analytics capabilities that allow you to make more informed business decisions. The software provides real-time insights into your business operations, which can help you identify areas for improvement.   4. Integration with Other Microsoft Products: Dynamics 365 Finance and Operations integrates with other Microsoft products such as Office 365, Power BI, and Azure, providing a seamless user experience and better collaboration across different teams and departments.   5. Continuous Updates and Support: With Dynamics 365 Finance and Operations, you will receive continuous updates and support from Microsoft. This means you will always have access to the latest features and functionalities, as well as any necessary security patches and bug fixes.   In summary, upgrading from Dynamics AX to Dynamics 365 Finance and Operations can provide several benefits, including a cloud-based solution, improved user interface, advanced reporting and analytics, integration with other Microsoft products, and continuous updates and support. 1. Functional Enhancements Few new features and functionalities those were not available in Microsoft Dynamics AX, that are now built-into Dynamics 365 Finance and Operations. Advance Warehousing Transportation Management Mobile Time sheet Project Enhancements Auto Bank Reconciliation Positive Pay Enhanced Financial Dimensions RFQ (request for quotation) Purchase Requisition Public Sector Azure Dev Ops Task Recorder Automated Testing Suite Global Address Book Office 365 Add-in Vendor Collaboration Portal Retail & POS Product Catalogs Trade Allowance There are many more additional functionalities available through App Source, from Microsoft and third-party providers. Of course, the framework exists to build your own in future. 2. Integrated Business Operations With Dynamics 365, people and processes are all integrated, resulting in a much better experience for your employees and your clients.   Your data and workflow seamlessly moves across all your departments. You get to build your software system according to your business operations, and not have to tweak or twist because of mosaic of systems you may have. Finance Operations Project Management Customer Service Talent Sales Field Service Retail 3. Business Insights With Dynamics 365, you can now easily realize the benefits of latest technologies like Artificial Intelligence and Machine Learning, Business Intelligence and Forecasting. Leverage the unlimited power of Flow (integration), PowerApps (extensibility) and Power BI (insights), giving your business a real advantage. 4. Web Client Modern & Mobile-friendly User Experience Dynamics 365 Finance and Operations has a user-friendly interface and is available anywhere, anytime, on any device. Savings on the user training and improved user productivity. 5. Microsoft Cloud Leader in the cloud space. Office 365 – Active Directory & Authentication Top quality infrastructure maintenance Scalability & flexibility Consistent Upgrades Built-in Disaster Recovery Cybersecurity Monitoring & Threat Management Intrusion detection & Ongoing Application Penetration testing 6. Cost of Ownership Freeing up your infrastructure workforce to work on other projects. Cloud model provides more visibility into the operating costs of your solution. Huge savings in the total cost of application (infrastructure, application maintenance, software license combined). 7. Support Lifecycle Support for Dynamics AX is nearing its end and current users are transitioning to D365 Finance and Operations. Software Patches, Application Updates, Security fixes would not be available in time or not at all. The Application Support resources and User forums will start drying up. Our Microsoft certified professionals are ready to guide you through the process, and request a personalized TCO comparison. About the Author Sohena Hafiz is the President at Ascent Innovations LLC.   Sohena has extensive experience both in Technical and Functional roles over 22 years delivering customer-centric solutions in Microsoft Dynamics AX and Dynamics 365 Finance & Operations. Author: Sohena Hafiz President Icon-linkedin Latest Posts You might also like:

by
If You Sense Problems in Your D365 Implementation, You Probably Have Them

If You Sense Problems in Your D365 Implementation, You Probably Have Them Table of Contents If You Sense Problems in Your D365 Implementation, You Probably Have Them ERP implementations are complex. Delays, budget overruns, and lack of progress don’t just happen randomly. If you’re noticing signs of trouble, chances are the problems already exist—and they’re growing. Most organizations don’t take action until issues become unavoidable. By then, recovery is costly, timelines are unmanageable, and executive confidence is eroding. The key to avoiding major failure is recognizing the warning signs early and acting before it’s too late. Top 5 Warning Signs Your D365 Project Is in Trouble 1. Unclear Business Objectives When asked, can your team articulate the business goals behind the implementation? If there’s hesitation, it’s a problem. A project without a clear, well-communicated vision will drift—features will be built that don’t serve the business, priorities will shift unpredictably, and leadership will struggle to measure success. What this leads to: Endless revisions and scope changes Disconnected business and technical teams A system that is functional but not useful 2. Persistent Project Delays Without Justifications Delays happen, but they should always have a clear reason and a corrective action plan. If deadlines are constantly shifting and explanations are vague, the project is already losing control. Endless revisions and scope changes Disconnected business and technical teams A system that is functional but not useful What this leads to: Rising costs with no clear ROI Low confidence from leadership and stakeholders Rushed decisions leading to poor implementation quality 3. Gaps in System Design and Customization A well-implemented ERP system should align with your actual business processes—not force users into workarounds. If teams are struggling with usability, or the system feels unnecessarily complicated, design issues may be at the core. Common red flags: Over-customization – When simple processes require excessive modifications, creating unnecessary complexity Under-customization – When critical business functions are missing, forcing teams to operate outside the system Lack of user input – Functional teams weren’t involved in the design phase, leading to misaligned workflows 4. Poor Testing and Quality Assurance Rushing through testing to keep the project “on track” is a critical mistake. If user acceptance testing (UAT) is inconsistent, errors keep resurfacing, or teams don’t trust the system, your project isn’t ready for go-live. Key risk areas: Unidentified integration issues with other systems Missing or incorrect data migration, leading to reporting errors Incomplete training, leaving users unprepared for real-world use 5. Low User Adoption and Resistance to Change The best ERP system is useless if people don’t use it. If end users are hesitant, reverting to old processes, or complaining about the system’s usability, adoption problems are emerging. This often happens due to: Inadequate training – Users weren’t prepared, so they default to manual workarounds Process misalignment – The system doesn’t fit their workflow, leading to frustration Lack of executive buy-in – Leaders haven’t reinforced the value of the system Cost of Ignoring the Signs These warning signs don’t fix themselves. The longer issues go unaddressed, the higher the recovery costs – both in budget and in business impact. If your D365 project is showing any of these signs, the best move is to act now. A structured, expert-led project assessment can uncover risks, define corrective actions, and reset the implementation on the path to success. Turning a Failing Project Around At Ascent Innovations, we specialize in rescuing D365 implementations before they spiral out of control. Our structured approach focuses on: Pinpointing root causes – A comprehensive project audit to identify critical gaps Developing a risk mitigation plan – Addressing overlooked requirements, system misalignment, and leadership gaps Rebuilding confidence – Establishing a realistic, achievable path to go-live with full executive alignment Fix the Problems Before They Cost More If you’re sensing trouble, it’s not just intuition—it’s a sign to act. A failing ERP project can drain resources, disrupt operations, and damage executive confidence. The sooner you assess the risks and take corrective action, the lower the cost and impact of recovery.   Experience has no alternative. If your D365 implementation is off track, we can help you get it back under control—before it’s too late. About the Author Kalyan Kumar is a Senior Consultant for D365 and AX implementations with a track record of over 30 successful ERP rollouts across industries, including manufacturing (discrete and process), service, trade and distribution, construction, real estate, and government. Kalyan Kumar Senior Consultant for D365 Latest Posts You might also like:

by
importing-custom-data-in-d365-data-entities

Importing custom data in D365 Data Entities Table of Contents Importing custom data in D365 Data Entities Every organization has custom data that is specific to their operations/process.   Most organizations see tremendous value in bringing over that data to work with your enterprise software system either interactively for transactions or use for reports/dashboards.   Microsoft Dynamics 365 Finance and Operations has provided a Data Management Framework (DMF), that allows for the D365 system to be that one fully-integrated & all-encompassing system.   We will walk through Data Management Framework of Dynamics 365 Finance & Operations. Data Management & Data Entity Data Management Framework of Microsoft Dynamics 365 for Finance and Operations utilizes data entities in Data migration Copy module setups and configurations Integrations In this example, we will see how data is imported through Data entity from an Excel file. Figure 1. Data Management in Dynamics 365 for Finance and Operations Sample Scenario D365 Finance & Operations allows for adding fields to existing Data entities, so most custom data can be included within that entity. For the sake of explaining the programming concept, we will create a new entity which is related to the existing master data entity, say Customer.   There are many scenarios where users bring data from external systems and import into D365 on a daily/weekly basis. Figure 2. Sample excel data The user will make a list of customer accounts available, in an excel file, and then import that file in Dynamics 365 for Finance and Operations using the Data management workspace through a Data Entity.   During the import, the system will find the related record of customer account in Customer master and store its record Id (CustTable.RecId) into a new table ASCCustRelatedTable as well as monthly account balance (and any other custom data fields). In case of any exception, user would able to view the error or warning details in the log of the Data management module. Building the solution First, we will create a table ASCCustRelatedTable with all the required fields and index where we store the values of CustTable.RecId during the time of import from excel. In our case, we have fields and index as mentioned here Figure 3. ASCCustRelatedTable structure Figure 4. View of ASCCustRelatedTable in the development window After creating the table ASCCustRelatedTable, we would be creating a data entity. For this we must right click on the table and go to Add-ins, then click on Create data entity. By doing this, new data entity ASCCustRelatedTableEntityalong with some dependent security privilege objects. Figure 5. Creating new entity from ASCCustRelatedTable Figure 6. New entity and security objects from ASCCustRelatedTable The user will only import an excel file that contains a list of customer account, but we require to store the record Id of Customer master (CustTable.RecId) into a separate table ASCCustRelatedTable as well as monthly account balance. To achieve this, we must create a new class ASCCustRelatedTableEntityEvents and subscribe MappingEntityToDataSource event of data entity ASCCustRelatedTableEntity.   We would be initializing the value of CustTableRecId and MAB fields through this MappingEntityToDataSourceevent which would be executed during the time of excel import.   Here is how the assignment would be CustTableRecId = CustTable.RecIdMAB = CustTable.BalanceCurrency() We can change and utilize the event as per your need and business scenarios. Figure 7. Assigning values to the fields of the ASCCustRelatedTable through MappingEntityToDataSource After all these steps, we should build and synchronize our Visual Studio solution. Testing Log in to your Microsoft Dynamics 365 for Finance and Operations environment & open the workspace Data management. Click on Import, choose the data entity ASCCustRelatedTableEntity and add your source excel file with the list of customers. Figure 8. Data management workspace – Import This is how the import project looks Figure 9. Data management – Import project Click on Import in the action pane and records will get inserted into the table ASCCustRelatedTable along with the field CustTableRecId and MAB. Figure 10. ASCCustRelatedTable table browser In case of an error, we can refer the log. Figure 11. Data management – Import project’s log information Author: Krish Moorthy Technical Specialist – Microsoft Dynamics 365 Latest Posts You might also like: