Powershell 7 Conflict?

[ryanlraines]

I'm getting this error when attempting to connect to an organization while using PowerShellv7. There are no issues when running from PowerShellv5.

The term 'Get-CrmConnection' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Environment:

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Get-InstalledModule

Version              Name                                Repository           Description
-------              ----                                ----------           -----------

2.8.8                Microsoft.Xrm.Data.Powershell       PSGallery            This module uses the CRM connection from Microsoft.Xrm.Tooling.CrmConnector.Powershell and provides common functions to create, delete, query, and update data

[sergeytunnik]

PSEdition Core

That means it runs in .net core. While D365 Xrm Sdk supports only full framework.
Couldn't quickly find If PowerShell 7 supports full .net framework.

[seanmcne]

This won't work today, powershell 7 uses .NET core 3.1. Once our product team releases a compatible .NET core library and connector then we can try to move to support it (that is going to be a while yet, it would be worth checking back in on this around the fall timeframe).

[seanmcne]

Duplicate of: #372 requesting for PowerShell 6

[dweddig01]

Any updates on PowerShell 7 support?

[tiktb8]

Also looking to use this in Azure Functions - any further update on PS 7/Core 3.1?

[seanmcne]

negative, the Microsoft provided Xrm tooling powershell connector (which is what this module relies on) is a .NET powershell module which isn't supported/won't work on PS Core, as far as I know.

[ppibeauty]

Now that powershell core v7 supports .net, can these be ported over?

https://docs.microsoft.com/en-us/powershell/scripting/whats-new/what-s-new-in-powershell-70?view=powershell-7.2

[seanmcne]

Can you be more specific to what is supported for .NET? Everything I'm seeing is Core 3.1 but there is better OOB module support for previous versions - I'm not aware of XRM Tooling supporting PowerShell 7 yet. I believe there is more work to do here before the xrm tooling powershell connector would work in PowerShell 7 - once it supports PowerShell 7 I think much of the functions/cmdlets are here. I may have misunderstood your question or reference though - let me know - thanks!

[mike9182]

Is there any update on this now that the Microsoft.PowerPlatform.Dataverse.Client package, which fully supports .net core, has been released?

Transition apps to Dataverse ServiceClient

[seanmcne]

This module uses XRM tooling PowerShell module published directly by Microsoft: https://www.powershellgallery.com/packages/Microsoft.Xrm.Tooling.CrmConnector.PowerShell/

If the connector module were to be updated, to run in other PowerShell runtime environments, I'd look at how to adapt this to work with that update.

[rvdwegen]

Respectfully, but perhaps its time for some internal pressure within Microsoft on this subject instead of a wait and see approach?

Personally I'm starting to run into situations where I would like to use certain other modules in combination with this one that aren't even compatible with versions of powershell below 7.0

[seanmcne]

Point taken @rvdwegen, as far as I know there isn't anything on the public roadmap w/ a target release date. If this changes I will happily update the issue here and hopefully we can work on a plan or figure out what needs to be done.

[improving-jeffd]

Any idea where one can see release notes for Microsoft.Xrm.Tooling.CrmConnector.PowerShell/?

I see it updated an hour ago, but only a build number increment. So not likely the big update that will unblock this I guess... It also still lists 5.1 as it's min PS Version.

[seanmcne]

If you expand Package Details it will show you the release notes.

[seanmcne]

FYI - I also updated the assemblies in the latest update branch here: https://github.com/seanmcne/Microsoft.Xrm.Data.PowerShell/tree/updateToAssemblies3.3.0.7128

You're welcome to download and test - I've been doing some tests locally trying to ensure everything works as expected (so far, so good).

[improving-jeffd]

Well now I feel dumb! LOL... Thanks! 😀

[seanmcne]

No worries, I had the previous release ready for an update but hadn't had time to test it and I just re-updated it with the recent package that was released (you didn't miss anything, I just happened to have it open and ready to go to rename and update 🙂).

[rvdwegen]

@seanmcne
Hey, I was wondering if you were aware of the work that is seemingly being done on a new Microsoft made module for Dataverse/CRM?

Its nested in this repo, https://github.com/microsoft/PowerPlatform-DataverseServiceClient/tree/master/src/GeneralTools/DataverseClient/PowerShell/Microsoft.PowerPlatform.Dataverse.Client.PowerShell/Microsoft.PowerPlatform.Dataverse.Client.PowerShell

[seanmcne]

@seanmcne Hey, I was wondering if you were aware of the work that is seemingly being done on a new Microsoft made module for Dataverse/CRM?

Its nested in this repo, https://github.com/microsoft/PowerPlatform-DataverseServiceClient/tree/master/src/GeneralTools/DataverseClient/PowerShell/Microsoft.PowerPlatform.Dataverse.Client.PowerShell/Microsoft.PowerPlatform.Dataverse.Client.PowerShell

Aware there is some work going on here, not sure the current state but I'm definitely supportive of the team utilizing what we've learned and are still learning here for a better first party solution! Everything provided in this module is a layer on top of the existing first party connector, in my opinion the work done here makes the first party module much more usable and hopefully, easier.