You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Import-CrmSolution/Import-CrmSolutionAsync currently give no feedback to the user unless they specifically use -Verbose, and Import-CrmSolutionAsync doesn't give any progress indication even when using -Verbose.
Powershell has a native progress indication mechanism, Write-Progress, which can be leveraged to provide the user feedback on solution import progress without filling up their prompt with progress messages.
Import-CrmSolutionAsync could also leverage the same logic as Import-CrmSolution to poll the import for progress if $conn.ImportSolutionToCrmAsync is used rather than manually generating an asyncoperation and submitting. ImportSolutionToCrmAsync outputs both the asyncoperation and importjob ID's, allowing us to poll the status of both to provide useful progress feedback to the user.
The text was updated successfully, but these errors were encountered:
Import-CrmSolution
/Import-CrmSolutionAsync
currently give no feedback to the user unless they specifically use-Verbose
, andImport-CrmSolutionAsync
doesn't give any progress indication even when using-Verbose
.Powershell has a native progress indication mechanism,
Write-Progress
, which can be leveraged to provide the user feedback on solution import progress without filling up their prompt with progress messages.Import-CrmSolutionAsync
could also leverage the same logic asImport-CrmSolution
to poll the import for progress if$conn.ImportSolutionToCrmAsync
is used rather than manually generating anasyncoperation
and submitting.ImportSolutionToCrmAsync
outputs both theasyncoperation
andimportjob
ID's, allowing us to poll the status of both to provide useful progress feedback to the user.The text was updated successfully, but these errors were encountered: