question

SusantoReza-8994 avatar image
0 Votes"
SusantoReza-8994 asked ·

Unable to Debug When Using Global Parameter with hyphens in its name in Expressions

Found this issue after many many hours of troubleshooting. When using a Global Parameter in an expression and the parameter name has 'hypens' I was unable to debug the pipeline with the following error:

 {"code":"BadRequest","message":null,"target":"pipeline//runid/dd8be58c-de84-458c-aace-xxxxxxxxx","details":null,"error":null}


Steps to reproduce:

  1. Create a Global Parameter with hyphens in its name e.g. 'global-parameter-name'

  2. Create a pipline, add a variable

  3. Add 'Set Variable' activity to assign the Global Parameter to that variable with an expression

  4. Debug the pipeline

Here's the sample pipeline

 {
     "name": "pipeline1",
     "properties": {
         "activities": [
             {
                 "name": "Set variable1",
                 "type": "SetVariable",
                 "dependsOn": [],
                 "userProperties": [],
                 "typeProperties": {
                     "variableName": "localVar",
                     "value": {
                         "value": "@pipeline().globalParameters.gbl-parameter-with-hypens",
                         "type": "Expression"
                     }
                 }
             }
         ],
         "variables": {
             "localVar": {
                 "type": "String"
             }
         },
         "annotations": []
     }
 }


Is this a bug? or did I miss something?


azure-data-factory
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

NandanHegde-7720 avatar image
0 Votes"
NandanHegde-7720 answered ·

Hey @SusantoReza-8994,
This is a known issue w.r.t parameters and variables wherein some characters like space or hypen do not work (Test 01 or Test-01).

there is another thread going on :
https://docs.microsoft.com/en-us/answers/questions/305526/paramter-passing-dataset.html
somewhat similar to this

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KranthiPakala-MSFT avatar image
0 Votes"
KranthiPakala-MSFT answered ·

Thanks @NandanHegde-7720 for sharing your insights and helping the community.

Hi @SusantoReza-8994, In addition to what @NandanHegde-7720 stated, as a good practice it is recommend to follow data flow transformation naming rules to name your pipeline parameters and variables. Please see this doc for more information: Azure Data Factory - naming rules

76424-image.png

If the above response from @NandanHegde-7720 was helpful, please do consider to accept answer and upvote on his post as it would be beneficial for other community members reading this thread.

Do let us know if you have further query.

Thank you


image.png (39.7 KiB)
· 4 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @SusantoReza-8994,

We still have not heard back from you. Just wanted to check if the above information was helpful? Do let us know if you have further query.

Thanks

0 Votes 0 ·

This looks like a bug IMHO, at the a very least the documentation should have been updated to specify this limitation. Good practice != requirement

Thanks for the answers guys!

0 Votes 0 ·

Hi @SusantoReza-8994,

Thanks for the feedback. I have already shared this feedback to ADF engineering team to thrown an inline error when a parameter name or a variable is created with an unsupported character or space in it.

Similar to below:


76922-image.png

I would also request you to please share your feedback in Azure Data Factory feedback forum: https://feedback.azure.com/forums/270578-azure-data-factory which ADF product team actively monitors and review them.

Also please do share the feedback link here once it is created, so that I can attach it to my internal escalation which would also help to prioritize the feature implementation.

Thank you.




0 Votes 0 ·
image.png (28.0 KiB)

We will work with the docs team to have a note about this limitation in the documentation. Thank you again for the feedback.

0 Votes 0 ·