After updating Power Automate Desktop to version 2.14.173.21294 last week, the action "Get File Path Part" changed behaviour in the sense that if a path given to it is not a valid file, any variables coming out of it come out blank, with no exception being thrown like it was on previous versions, which can lead into a debug nightmare as the flow just proceeds until it throws error somewhere else because of the empty generated variables (Directory, Filename, etc...).
In fact, in Winautomation, this action performed differently, as it, not just it didn't care if the file path given existed, but also it would work in folder paths as well, so a very easy way to navigate through long nested folder hierarchies and get parent folder names, etc (which I need very often)
Example:
C:\Users\myuser\OneDrive\Documents\folderONE\FolderTwo
running the action once would output
"FolderTwo" as "FileName"
"C:\Users\myuser\OneDrive\Documents\folderONE as "Directory"
If you did run it again using "Directory" as the path, it would output:
"FolderONE" as "FileName"
"C:\Users\myuser\OneDrive\Documents\ as "Directory"
This was a very easy to breakdown long nested file paths, instead of having to use splits, loops and joins, with the only drawback being that it did not check the if the path given was a valid existent file, but that could be obviously done by "If file exists" if needed.
The last version of PAD doesn't do any of this.
