That actually doesn't address the issue. This is an instance of specifically making a change from the web platform (which DOES detect the change - hence the message) and propagating it outward to slaved folders presumably on PCs. If this were a change in the reverse direction your point would make sense. Because the change was detected, it CAN be enforced and applied downstream to all connected PCs.
OK, again: The unspoken workaround would then be to have a script add a character with the case change. Apply the update. Then remove the added character and apply that update. Which is what I have to do. Which is my entire point. Automate the extra step instead of automating the very specific error notification (which is itself an extra step). If I am capable of performing the action, the interface is capable of performing the action Q.E.D. The entire point of designing a user front end is to work around file system limitations such as this. It is why we no longer administer our own multi connection ftp accounts and use Dropbox in the first place.