So, I was doing some testing with a new Flow in Power Automate. What I wanted it to do was, at a recurring time each day, look for today’s date in a list of SharePoint items and then display other values from any matching record in a Team’s chat. To prototype this out I created a very simple list with two columns, as shown above, Title and Date. Remember, the Title field is generally created for you by default when you create a basic SharePoint List.
In Power Automate I used a SharePoint Get Items action as shown above to get the information I wanted. To filter down to the data I used on ODATA query like:
Date eq ‘2021-12-31’
to test. Problem was, as shown above, I was getting no results that were feeding through to the next Apply to each action that followed directly after.
There were no errors indicated in my Flow. I tried a number of different format options and so on, trying to work out what the issue was.
The issue turned out to be the name of the field – Date – I had created in my SharePoint List! Once I created a new column called Dateoption with the same format, and entered the same data into it and removed the offending Date column, it successfully filtered data as expected and passed the result to the following Apply to each action as you can see above.
The moral of the story is that you should probably avoid naming your fields with any ‘reserved’ programming commands like ‘Date’ as I did. Make it something unique like ‘Datefield’ or whatever. Just don’t use a common term like ‘Date’ as I did or you might struggle to troubleshoot as I did here.
Hopefully, this will save you wasting the amount of time I did to solve this that you can better spend on creating your Flow!
I’m joined by Vic Perdana from Microsoft to speak about Azure cost management. Many people have shied away from Azure over price blow out concerns. The good news is that Azure has all the tools you need to successfully manage your costs and with the help of some techniques that Vic shares with us in this podcast, you should never have to worry again.
As the end of year approaches, I share a little bit of news and updates as well as taking this opporunity to thank everyone for listening in 2021 and stay tuned for more in 2022.
The Word document Backdoor drop will download and open a Word document that contains a macro that will itself, download an EXE file to the desktop.
The PowerShell script fileless attack if successful will open Notepad.exe on the device.
The Dump credentials using SQLDumper.exe will download the SQL utility SQLDumper.exe and use that to try and dump the credentials from the the system LSASS.EXE process.
All the tests are benign and designed to firstly, test your environment again common breach techniques and secondly, to generate alerts in your environment to ensure your protection is correctly configured.
It is getting hard for me to determine all the outcomes of these tests, so I’d love to hear any feedback you have on your own results so I can improve the script. Also, if you have any suggestions for what tests you’d like to see included please let me know.
In next month’s Tech Dojo, since it is still the holiday season, we take a look at doing a Crypto 101 session. You’ll learn about coins, storage, NFTs, smart contracts and more. All for information and not investment advice. Come learn about the exciting world of blockchain.