-
Notifications
You must be signed in to change notification settings - Fork 0
Invoke D365DBSyncPartial
Invoke the synchronization process used in Visual Studio
Invoke-D365DbSyncPartial [[-SyncList] <String[]>] [[-SyncExtensionsList] <String[]>] [[-SyncMode] <String>]
[[-Verbosity] <String>] [[-BinDirTools] <String>] [[-MetadataDir] <String>] [[-DatabaseServer] <String>]
[[-DatabaseName] <String>] [[-SqlUser] <String>] [[-SqlPwd] <String>] [[-LogPath] <String>]
[-ShowOriginalProgress] [-OutputCommandOnly] [<CommonParameters>]
Uses the sync.exe (engine) to synchronize the database for the environment
Invoke-D365DBSyncPartial -SyncList "CustCustomerEntity","SalesTable"
This will invoke the sync engine and have it work against the database. It will run with the default value "PartialList" as the SyncMode. It will run the sync process against "CustCustomerEntity" and "SalesTable"
Invoke-D365DBSyncPartial -SyncList "CustCustomerEntity","SalesTable" -Verbose
This will invoke the sync engine and have it work against the database. It will run with the default value "PartialList" as the SyncMode. It will run the sync process against "CustCustomerEntity" and "SalesTable"
It will output the same level of details that Visual Studio would normally do.
Invoke-D365DBSyncPartial -SyncList "CustCustomerEntity","SalesTable" -SyncExtensionsList "CaseLog.Extension","CategoryTable.Extension" -Verbose
This will invoke the sync engine and have it work against the database. It will run with the default value "PartialList" as the SyncMode. It will run the sync process against "CustCustomerEntity", "SalesTable", "CaseLog.Extension" and "CategoryTable.Extension"
It will output the same level of details that Visual Studio would normally do.
The list of objects that you want to pass on to the database synchronoziation engine
Type: String[]
Parameter Sets: (All)
Aliases:
Required: False
Position: 1
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseThe list of extension objects that you want to pass on to the database synchronoziation engine
Type: String[]
Parameter Sets: (All)
Aliases:
Required: False
Position: 2
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseThe sync mode the sync engine will use
Default value is: "PartialList"
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 3
Default value: PartialList
Accept pipeline input: False
Accept wildcard characters: FalseParameter used to instruct the level of verbosity the sync engine has to report back
Default value is: "Normal"
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 4
Default value: Normal
Accept pipeline input: False
Accept wildcard characters: FalsePath to where the tools on the machine can be found
Default value is normally the AOS Service PackagesLocalDirectory\bin
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 5
Default value: $Script:BinDirTools
Accept pipeline input: False
Accept wildcard characters: FalsePath to where the tools on the machine can be found
Default value is normally the AOS Service PackagesLocalDirectory
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 6
Default value: $Script:MetaDataDir
Accept pipeline input: False
Accept wildcard characters: FalseThe name of the database server
If on-premises or classic SQL Server, use either short name og Fully Qualified Domain Name (FQDN)
If Azure use the full address to the database server, e.g. server.database.windows.net
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 7
Default value: $Script:DatabaseServer
Accept pipeline input: False
Accept wildcard characters: FalseThe name of the database
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 8
Default value: $Script:DatabaseName
Accept pipeline input: False
Accept wildcard characters: FalseThe login name for the SQL Server instance
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 9
Default value: $Script:DatabaseUserName
Accept pipeline input: False
Accept wildcard characters: FalseThe password for the SQL Server user
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: 10
Default value: $Script:DatabaseUserPassword
Accept pipeline input: False
Accept wildcard characters: FalseThe path where the log file(s) will be saved
When running without the ShowOriginalProgress parameter, the log files will be the standard output and the error output from the underlying tool executed
Type: String
Parameter Sets: (All)
Aliases: LogDir
Required: False
Position: 11
Default value: $(Join-Path -Path $Script:DefaultTempPath -ChildPath "Logs\DbSync")
Accept pipeline input: False
Accept wildcard characters: FalseInstruct the cmdlet to show the standard output in the console
Default is $false which will silence the standard output
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalseInstruct the cmdlet to only output the command that you would have to execute by hand
Will include full path to the executable and the needed parameters based on your selection
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
Tags: Database, Sync, SyncDB, Synchronization, Servicing
Author: Mötz Jensen (@Splaxi)
Author: Jasper Callens - Cegeka
Inspired by: https://axdynamx.blogspot.com/2017/10/how-to-synchronize-manually-database.html
- 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