![]() The Excel connector is very troublesome, and in a perfect world we wouldn't have to use it - and I'm hoping that we eventually move this process to a REST API operation. The merge functionality isn't reliable enough for us. You may be able to get the table and spreadsheet to merge nightly, but again, we've found that purging the list daily is the best way to insure that we truly have reliable data daily. It sounds like your email that comes in daily may have spreadsheets that are named differently, and possibly have different table names, but the process should still pretty much be the same, you just need to add the logic to figure out the names, and/or add a step to the dowload Flow that renames the file/table names before uploading the Excel file to the document library. ![]() I've added screenshots of our Purge and Upload Flows, which hopefully may help. For one reason or another, we do have failures every so often but this allows us to remedy those failures right away. You can certainly build all of this functionality into a single Flow, but I like having the ability of knowing right away if/when each step of the process fails. This combination works great for us, and has for months. The Purge flow runs in about 30 seconds, and and the Upload flow runs in about 60 seconds. Then, the "Purge" Flow happens at midnight, with the "Upload" Flow happening 15 mintues later. The "Download" Flow runs nightly at 10:00PM (a few hours after our client publishes the file every night). You can set the Trigger to be when a new file is added to the Document Library, or you could schedule it at a certain time daily.įor us, we perform all of this on a recurring schedule. Third Flow: The third flow is to upload the Excel table to the now empty SharePoint List on a recurring schedule.So we created a SharePoint "Purge List" Flow that deletes all rows from the List daily (right before we upload the new list items). I've found, that merging changes from an Excel file to a SharePoint Online List is nearly impossible - because it simply isn't reliable. Second Flow: Purge the SharePoint List.Then have the Flow upload that Excel file to a document library. You could do this by monitoring the FROM address, or the attachment type, Subject name, etc. First Flow: Create a flow to monitor your email to grab the Excel file daily.You likely need three different Flows to perform this task, which would be: These resources will help you avoid common import errors. Read the Instructions page in the file, and see The Excel template for Shifts. You can either work directly in the exported file, or use Save as to create a second copy of the file for editing. Select Enable Editing at the top of the page. No-code required.I have a similiar workload that I do daily, outside of getting the file from an email every day - I grab it from an FTP. Open the Excel workbook you exported from Shifts. WorkApps Package your entire business program or project into a WorkApp in minutes.Digital asset management Manage and distribute assets, and see how they perform.Resource management Find the best project team and forecast resourcing needs.Intelligent workflows Automate business processes across systems.Governance & administration Configure and manage global controls and settings.Streamlined business apps Build easy-to-navigate business apps in minutes.Integrations Work smarter and more efficiently by sharing information across platforms.Secure request management Streamline requests, process ticketing, and more.Process management at scale Deliver consistent projects and processes at scale. ![]() Content management Organize, manage, and review content production.Workflow automation Quickly automate repetitive tasks and processes. ![]() Team collaboration Connect everyone on one collaborative platform.Smartsheet platform Learn how the Smartsheet platform for dynamic work offers a robust set of capabilities to empower everyone to manage projects, automate workflows, and rapidly build solutions at scale.
0 Comments
Leave a Reply. |