Azure-docs: Default Value of Variables

[Hasil-Sharma]

Hey !

I want to directly assign values passed as parameters to variables. To keep things cohesive, I only want to use variables in my pipeline. One obvious way to assign parameter value to a variable, a Set Variable activity.

Another way is via "defaultValue" attribute in variables. In case of string parameters, I can do this by adding @{pipeine().parameters.<< parameterName >>} to defaultValue of a variable, and value of variable becomes same as that of parameter.

For example, consider eventEndTime as a parameter of type string to my pipeline, if I do following the value passed for this parameter gets assigned to the variable EventEndTime automatically without a Set Variable activity.

"EventEndTime": {
                "type": "String",
                "defaultValue": "@{pipeline().parameters.eventEndTime}"
            }

How to do the same in case my parameter is of type Array instead of String?

Additionally, I know there is a limit of 50 parameters per pipeline, is their a similar limit on number of variables too?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 76e31411-f1a2-710b-94c0-39acf9e7314b
• Version Independent ID: d5cefffe-dee0-2d2e-f3cb-8eefd5d40d17
• Content: Expression and functions in Azure Data Factory - Azure Data Factory
• Content Source: articles/data-factory/control-flow-expression-language-functions.md
• Service: data-factory
• GitHub Login: @djpmsft
• Microsoft Alias: daperlov

[AjayKumar-MSFT]

@Hasil-Sharma, Thanks for the feedback! We are taking a look into this and will get back to you soon.

[MartinJaffer-MSFT]

@Hasil-Sharma Thank you for bringing this interesting issue to our attention. I have tried assigning expressions to array type variable default values, and run into the same issue. I will reach out internally for more info.

[MartinJaffer-MSFT]

@Hasil-Sharma The developers have added to their backlog, a work item to allow you to assign the default value for array type variables, just like you are for string type variables. No ETA at this time.

Until then, you will need to use the Set Variable activity.

I did not hear back on the maximum number of variables. I did a test. I created a pipeline with ~53+ parameters and ~53 variables+. No errors were thrown when I debugged.

[Hasil-Sharma]

Thanks, Martin. Appreciate your efforts.

Not a blocker for me, though important as number of activities per pipeline are limited to 50 and using limited slots for Set-Variable activity to do a direct assignment seems to a drawback.

please-close