PowerShell SnapIn vs "Minimal version" Bug

Hi RDM Support

This is a very minor bug only, and may not be urgent to fix, but I wanted to report it anyway...

When I configured my Data Source, I set up some options in the "Data Source Settings" screen. One of the things I ticked was "Minimal version", and set it to "Current" (8.4.5.0 in my case). I also set the "Client install path/URL" so that users would be prompted with the location of an install package should their client not be recent enough.

Later on, when I started doing some PowerShell scripting, I couldn't get it to work! Then I realised that every time I tried to PowerShell something, a Windows Explorer window would open up, in the folder that I had specified in the "Client install path/URL" setting. It took me a while to realise what was happening - the PowerShell script was being rejected because it wasn't the right version!

Once I removed the "Minimal version" tick, everything worked fine.

Regards
Des