🚸 All cmdlets with module/model parameters should support ValueFromPipelineByPropertyName and ValueFromPipeline

[FH-Inway]

There are multiple cmdlets that have a (often mandatory) Module and/or Model parameter. Some of those cmdlets decorate those parameters with the ValueFromPipelineByPropertyName and/or ValueFromPipeline attributes. This makes the cmdlets easy to use in combination with other cmdlets that return a list of modules, such as Get-D365Module.

To provide a consistent user experience, it would be nice if all cmdlets support the ValueFromPipeline* options.

I.e. one can do
Get-D365Module -Name "MyPrefix*" | Invoke-D365ModuleFullCompile
but not
Get-D365Module -Name "MyPrefix*" | Invoke-D365ProcessModule -ExecuteCompile

[Splaxi]

I'm all in favor, but don't have an overview of how much work this will require.

Happy to split the workload between us, so you don't have to do all the heavy lifting yourself...

[FH-Inway]

I will compile a list of cmdlets that we should look at. Searching for "[string] $Module" in the functions seems to be a good starting point. Finds 13 files and about half of them already have pipeline support.