From the Microsoft Power Platform blogs: Recurring and EOM dates; Posting to a Copilot Studio agent; Power Automate cloud flow failing; AI-powered search

In this week's Power Platform blogs: 

• Power Apps EDate and EOMonth: how to handle recurring and end-of-month dates
• 'We couldn't find your bot' when posting to a Copilot Studio agent from a cloud flow
• Power Automate cloud flow failing with 403 forbidden on a Dataverse action
• Add AI-powered search capabilities to your Power Pages Site

Power Apps EDate and EOMonth: how to handle recurring and end-of-month dates

On the PowerApps911 blog, Shane Young wrote that if you've ever tried to schedule something that repeats on the 30th or 31st of the month, you know the problem. 

Young stated that a subscription might start on January 30, and the next payment is supposed to be one month later. But February doesn't have a 30th. So which date should you use, and how can you get Power Apps to calculate it without writing a lot of if-statements?

According to Young, two functions make this easy: EDate and EOMonth. He noted that they work much like the same functions in Excel and handle most of the date calculations for you. 

In his post, Young explained what each function does and when to use it. He also offered a few helpful techniques using Sequence and AddColumns that make it easy to test how they work.

'We couldn't find your bot' when posting to a Copilot Studio agent from a cloud flow

Writing