With the number of PS modules available, there are bound to be some name collisions going to happen.
There are a number of solutions:
- Use the Prefix parameter on the Import-Module cmdlet.
- Use the fully qualified name (modulename\cmdletname), as you did
- Check if the module comes with a builtin prefix (the DefaultCommandPrefix setting in the module's manifest file). Also present on the object returned from Import-Module
- Make sure that one of the modules with the conflicting cmdlet is not loaded. Which might be a bit of a challenge with module autoloading and the cache it uses.