-
Notifications
You must be signed in to change notification settings - Fork 102
Get D365Module
Get installed package / module from Dynamics 365 Finance & Operations environment
Get-D365Module [[-Name] <String>] [-ExcludeBinaryModules] [-InDependencyOrder] [[-BinDir] <String>]
[[-PackageDirectory] <String>] [<CommonParameters>]
Get installed package / module from the machine running the AOS service for Dynamics 365 Finance & Operations
Get-D365Module
Shows the entire list of installed packages / modules located in the default location on the machine.
A result set example:
ModuleName IsBinary Version References
AccountsPayableMobile False 10.0.9107.14827 {ApplicationFoundation, ApplicationPlatform, Appli... ApplicationCommon False 10.0.8008.26462 {ApplicationFoundation, ApplicationPlatform} ApplicationFoundation False 7.0.5493.35504 {ApplicationPlatform} ApplicationFoundationFormAdaptor False 7.0.4841.35227 {ApplicationPlatform, ApplicationFoundation, TestE... Custom True 10.0.0.0 {ApplicationPlatform}
Get-D365Module -ExcludeBinaryModules
Outputs the all packages / modules that are NOT binary. Will only include modules that is IsBinary = "False".
A result set example:
ModuleName IsBinary Version References
AccountsPayableMobile False 10.0.9107.14827 {ApplicationFoundation, ApplicationPlatform, Appli... ApplicationCommon False 10.0.8008.26462 {ApplicationFoundation, ApplicationPlatform} ApplicationFoundation False 7.0.5493.35504 {ApplicationPlatform} ApplicationFoundationFormAdaptor False 7.0.4841.35227 {ApplicationPlatform, ApplicationFoundation, TestE...
Get-D365Module -InDependencyOrder
Return packages / modules in dependency order, starting with modules with no references to other modules.
A result set example:
ModuleName IsBinary Version References
ApplicationPlatform False 7.0.0.0 {} ApplicationFoundation False 7.0.0.0 {ApplicationPlatform} ApplicationCommon False 10.21.36.8818 {ApplicationFoundation, ApplicationPlatform} AppTroubleshootingCore False 10.21.1136.2... {ApplicationCommon, ApplicationFoundation, Applica...
Get-D365Module -Name "Application*Adaptor"
Shows the list of installed packages / modules where the name fits the search "Application*Adaptor".
A result set example:
ModuleName IsBinary Version References
ApplicationFoundationFormAdaptor False 7.0.4841.35227 {ApplicationPlatform, ApplicationFoundation, TestE... ApplicationPlatformFormAdaptor False 7.0.4841.35227 {ApplicationPlatform, TestEssentials} ApplicationSuiteFormAdaptor False 10.0.9107.14827 {ApplicationFoundation, ApplicationPlatform, Appli... ApplicationWorkspacesFormAdaptor False 10.0.9107.14827 {ApplicationFoundation, ApplicationPlatform, Appli...
Name of the package / module that you are looking for
Accepts wildcards for searching. E.g. -Name "Application*Adaptor"
Default value is "*" which will search for all packages / modules
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 1
Default value: *
Accept pipeline input: False
Accept wildcard characters: False
Instruct the cmdlet to exclude binary modules from the output
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
Instructs the cmdlet to return modules in dependency order, starting with modules with no references to other modules.
Type: SwitchParameter
Parameter Sets: (All)
Aliases: Dependency
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
The path to the bin directory for the environment
Default path is the same as the AOS service PackagesLocalDirectory\bin
Default value is fetched from the current configuration on the machine
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 2
Default value: "$Script:BinDir\bin"
Accept pipeline input: False
Accept wildcard characters: False
Path to the directory containing the installed package / module
Normally it is located under the AOSService directory in "PackagesLocalDirectory"
Default value is fetched from the current configuration on the machine
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 3
Default value: $Script:PackageDirectory
Accept pipeline input: False
Accept wildcard characters: False
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
Tags: PackagesLocalDirectory, Servicing, Model, Models, Package, Packages
Author: Mötz Jensen (@Splaxi)
Author: Martin Dráb (@goshoom)
The cmdlet supports piping and can be used in advanced scenarios. See more on github and the wiki pages.
- Install as a non-Administrator
- Install as a Administrator
- Import d365fo.tools module
- List available commands from d365fo.tools module
- Get help content for a command
- Start, Stop and List services
- Import users into the D365FO environment
- Import external users into the D365FO environment
- Enable users in the D365FO environment
- Update users in the D365FO environment
- Provision D365FO environment to new Azure AD tenant
- Import a bacpac file into a Tier1 environment
- List modules / models
- Compile module
- Install AzCopy
- Install SqlPackage
- Install Nuget
- Speed up LCS download via AzCopy
- Download latest bacpac from LCS via AzCopy
- Register NuGet source
- Configure Azure Logic App
- Fix AzureStorageConfig
- Run a runnable class
- Update users in environment
- Work with Azure Storage Account
- Work with packages, resource label files, language and lables
- Working with the different D365 services