Open ssisjoost opened 1 year ago
Thank you for your feedback. This has been routed to the support team for assistance.
@ssisjoost Thanks for the feedback! Looks like the issue is with the underlying .NET SDK used by the PowerShell cmdlet. We will share updates as we get this fixed.
Solved. A hardcoded value from an activity property was accidentally put in the expression override. So the expresion contained a hardcoded text. Synapse did always ran succesfully and the hardcode text was just honered. Even the build was successful.
I just checked each single pipeline with the Get-AzSynapsePipeline -Name "xxxxxx" until I found one pipeline failing... removed it and then the Get-AzSynapsePipeline without the name filter ran succesful. After that just check every activity/property until I found the mistake.
Can we hope for a fix. Like ever?
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @wonner, @v-yanjungao.
Description
Get-AzSynapsePipeline -WorkspaceName "xyz-we-a-saw-dp" always gives an error
Get-AzSynapsePipeline : The requested operation requires an element of type 'String', but the target element has type 'Object'. At line:7 char:1
unless you also provide the NOT mandatory name parameter: Get-AzSynapsePipeline -WorkspaceName "xyz-we-a-saw-dp" -Name "PL_Master"
Which is useless if you need ALL pipelines.
Tried also older versions of the module and both Powershell 5 and Powershell core
Issue script & Debug output
Environment data
Module versions
Error output