Releases: seanmcne/Microsoft.Xrm.Data.PowerShell
Releases · seanmcne/Microsoft.Xrm.Data.PowerShell
v2.8.19
Changes and enhancements in this release (also published on powershell gallery):
- Changed Enable-CrmLanguagePack to use Async it will prevent PowerShell timeouts and make it consistent with the same action taken in the UI
- For samples visit the community sample site here: https://github.com/seanmcne/Microsoft.Xrm.Data.PowerShell.samples
- Including latest xrm tooling 3.3.0.964 review the following website for release notes: https://www.powershellgallery.com/packages/Microsoft.Xrm.Tooling.CrmConnector.PowerShell/
v2.8.14
v2.8.13
release 2.8.11 fixing connection timeout parameter
fixing bug: connection timeout parameter was not working in 2.8.10
Release v2.8.10
semi-significant changes to connect-crmonline to take advantage of newer versions of ADAL capabilities. The module should now be capable of re-using cached tokens and signing in as the user who is signed into the PC. All of this should be backwards compatible.
2.8.10 - fixed bug with new-crmrecord identified in #432
2.8.9 Changes to connect-crmonline:
- Enable new CDS/CRM/D365 region TLD
- Force oAuth now can either use a credential provided which uses the username/pw in the connection string or it can be used without a credential and will natively use adal to get the username and password.
- NOTE: the username parameter and no credential provided SSO auth flow are designed for desktop use (interactive). If you are using this in dev ops or in a scripted process you'll still want to use credentials (which will continue to function without updates/changes)
- To avoid confusion and a couple issues a new username parameter was added, username can be provided with no password and will guide adal on which identity to attempt authentication for. If you are signed in with your current identity which has access to a given tenant it should just 'work' with or without the username.
- Default to oAuth if the UserName parameter is provided, even if you don't provided the forceoAuth switch, using a username parameter will assume you want to use modern auth
- New switch parameter BypassTokenCache will null out the token cache path if you're using azure dev ops this switch may be of importance to use to avoid token caching trying to access a path that doesn't exist on the sandboxed build host
- New integer parameter ConnectionTimeoutInSeconds can now be used to set the connection when you first connect
- New string parameter LogWriteDirectory can be used to force the module to write logs to a specific directory
- NOTE: Force discovery will force you to provide a credential, not sure if this is a bug in the connector, but it appears a credential is required, that said, if you're using ForceDiscovery, I suggest dropping it as forcing a discovery upon connecting is redundant and shouldn't be required - if you have a scenario where discovery is required please let me know (i'm considering removing this).
- Finally, I've added an experimental parameter set where you can provide a custom connection string. Please don't use this unless your debugging, I might change it later and wouldn't want to break anyone. If you require the use of a connection string directly can you let me know why so I can better accommodate? Thanks!
2.8.9 Other changes:
- Verbose parameter on connect-crmonline will output to a log file now in the local directory
- changed the object template for crmserviceclient to include the last error - the template is applied to avoid showing the auth token by default and clean up the output when the connection object is returned.
Updated release 2.8.9
semi-significant changes to connect-crmonline to take advantage of newer versions of ADAL capabilities. The module should now be capable of re-using cached tokens and signing in as the user who is signed into the PC. All of this should be backwards compatible.
Changes to connect-crmonline:
- Enable new CDS/CRM/D365 region TLD
- Force oAuth now can either use a credential provided which uses the username/pw in the connection string or it can be used without a credential and will natively use adal to get the username and password.
- NOTE: the username parameter and no credential provided SSO auth flow are designed for desktop use (interactive). If you are using this in dev ops or in a scripted process you'll still want to use credentials (which will continue to function without updates/changes)
- To avoid confusion and a couple issues a new username parameter was added, username can be provided with no password and will guide adal on which identity to attempt authentication for. If you are signed in with your current identity which has access to a given tenant it should just 'work' with or without the username.
- Default to oAuth if the UserName parameter is provided, even if you don't provided the forceoAuth switch, using a username parameter will assume you want to use modern auth
- New switch parameter BypassTokenCache will null out the token cache path if you're using azure dev ops this switch may be of importance to use to avoid token caching trying to access a path that doesn't exist on the sandboxed build host
- New integer parameter ConnectionTimeoutInSeconds can now be used to set the connection when you first connect
- New string parameter LogWriteDirectory can be used to force the module to write logs to a specific directory
- NOTE: Force discovery will force you to provide a credential, not sure if this is a bug in the connector, but it appears a credential is required, that said, if you're using ForceDiscovery, I suggest dropping it as forcing a discovery upon connecting is redundant and shouldn't be required - if you have a scenario where discovery is required please let me know (i'm considering removing this).
- Finally, I've added an experimental parameter set where you can provide a custom connection string. Please don't use this unless your debugging, I might change it later and wouldn't want to break anyone. If you require the use of a connection string directly can you let me know why so I can better accommodate? Thanks!
Other changes:
- Verbose parameter on connect-crmonline will output to a log file now in the local directory
- changed the object template for crmserviceclient to include the last error - the template is applied to avoid showing the auth token by default and clean up the output when the connection object is returned.
ClientSecret and solution publish and library Updates
- Add ClientSecret auth to connect-crmonline
- Updating help file and module parameter list/order for connect cmdlet
- Added Merge-HoldingSolution function
- Fixed log issues in Import-CrmSolutionAsync function
- Resolved other minor log issues to improve code readability
Timeout Change
This release includes:
- Switching how timeouts are set, maintained old process but added the following to ensure timeouts are working as expected: using https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.tooling.connector.crmserviceclient.maxconnectiontimeout?view=dynamics-xrmtooling-ce-9
- Updating binaries, sourced from: https://www.powershellgallery.com/packages/Microsoft.Xrm.Tooling.CrmConnector.PowerShell/3.3.0.862
- Added parameter for isenabledforallroles (#346)
- Update files to use UTF-8 encoding (#363)
- Change Dissociate and Associate record method to trigger message in CRM (#360)
Updated release 2.8.3
-
Updating to all the most recent versions of the binaries, sourced from: https://www.powershellgallery.com/packages/Microsoft.Xrm.Tooling.CrmConnector.PowerShell/3.3.0.862
-
Added parameter for isenabledforallroles (#346)
-
Update files to use UTF-8 encoding (#363)
-
Change Dissociate and Associate record method to trigger message in CRM (#360)
Incremental fixes & improvements
Shipping changes:
- #335 - Added additional system settings
- #337 / #338 - fix for long time bug with: Get-CRMSystemSettings : Cannot bind argument to parameter 'Name' because it is null.
If you notice any new issues please try a previous version and offer up any relevant details under the issues tab - thanks!