SharePoint and Power Platform related Stuff

Saving email attachments manually and filing them into dedicated directories quickly becomes tedious. With Microsoft Power Automate Desktop (PAD), you can build an automated workflow that fetches unread emails, downloads their attachments, and dynamically creates folders named after each file to keep your local storage tidy. Workflow Overview The automation performs the following sequence: Opens Microsoft Outlook. Retrieves unread emails from the inbox and saves attached files to a temporary directory. Extracts the base filename and the complete filename using Regular Expressions (Regex). Creates a new subfolder named after the attachment. Moves the downloaded attachment into its newly generated folder. Step-by-Step Implementation Step 1: Launch Outlook & Retrieve Messages Add the Launch Outlook action to store the session instance in %OutlookInstance% . Add the Retrieve email messages from Outlook action: Outlook Instance: %OutlookInstance% Account: your-email@domain.com M...

  Regex in Power Automate Desktop: A Practical Guide to Capturing Text Regular Expressions, commonly known as Regex , are extremely useful when working with text in Power Automate Desktop (PAD) . They allow you to find, identify, and extract specific information from unstructured text such as PDF documents, invoices, bank statements, emails, reports, and forms. In this guide, we will cover the most commonly used Regex patterns for Power Automate Desktop, with practical examples that can be directly applied to automation projects. http://regexstorm.net/tester https://regex101.com/ What is Regex? A Regular Expression is a pattern used to search for specific text or values within a larger block of text. For example, suppose a PDF contains: Customer ID: XXXXX1234 Account No: 99991XXXXX10099 PAN: 12XXXXXXXK Instead of manually searching for these values, Regex can automatically identify and extract them. For example: Customer\s+ID\s*:\s*(\S+) returns: XXXXX1234 Similarly: Account\s+No\....

  One of the most frustrating experiences in Power Automate is when a flow that has been running perfectly suddenly starts failing after a seemingly harmless change to a SharePoint List . Recently, I encountered exactly this scenario, and the solution turned out to be much simpler than I expected. The Scenario Imagine you have a flow triggered by the "When an item is created or modified" SharePoint trigger. Everything works perfectly until someone updates the SharePoint list schema. For example: A Person or Group column is changed from Single User to Allow Multiple Users . A column type is modified. Certain field settings are updated. Although the trigger itself doesn't change, the flow may still begin to fail because it continues referencing the old SharePoint schema . Why Does This Happen? Power Automate stores metadata about the SharePoint list when the trigger is configured. If the list schema changes later, the flow doesn't always refresh that metadata automa...