ADF GLobal Parameters error after trigger (debug works fine)

Question

ADF GLobal Parameters error after trigger (debug works fine)

markharing@bisqq.nl 61

Hi,

I have set a Global Parameter "maximale_ouderdom" which I use in an If Condition.

When I debug the pipeline all works fine. The global parameter is being used in the condition.

However, when the actual operational trigger is being used, the global parameter is not recognized anymore;

This is the full error message;

Error
Operation on target Controleer laatste wijziging failed: The expression 'lessOrEquals(activity('lookup_wijzigdatum').output.firstRow.OuderdomUren,pipeline().globalParameters.maximale_ouderdom)' cannot be evaluated because property 'maximale_ouderdom' doesn't exist, available properties are ''.

How is this possible? Am I doing something wrong?

HarithaMaddi-MSFT 10,146 Reputation points

2020-09-17T09:15:13.77+00:00

Hi @markharing@bisqq.nl ,

Welcome to Microsoft Q&A Platform.

Trigger in Azure Data Factory usually uses the last published configuration for pipelines. I see that you are using master as the branch and assuming that would be collaboration branch as well. Please let me know if publishing the changes is helping to run trigger successfully.
markharing@bisqq.nl 61 Reputation points

2020-09-17T09:47:53.697+00:00

@HarithaMaddi-MSFT

I have published the lasted version to the master branch on Github and I am still facing the same issue.
HarithaMaddi-MSFT 10,146 Reputation points

2020-09-17T11:02:34.837+00:00

@markharing@bisqq.nl - This is strange. I could not reproduce this issue in my data factory. Can you please share the JSON code of the pipeline as a text file here that helps investigating it.
markharing@bisqq.nl 61 Reputation points

2020-09-17T12:34:57.393+00:00

I have attached the JSON code of the specific pipeline.25419-controle-laatste-wijziging.txt
HarithaMaddi-MSFT 10,146 Reputation points

2020-09-17T12:55:32.227+00:00

@markharing@bisqq.nl - Thanks for sharing the JSON and I tried triggering the same pipeline from my data factory and it worked fine. Since this would need more investigation, can you please send a mail to AzCommunity[at]microsoft[dot]com with Subject: "Attn:Haritha - ADF GLobal Parameters error after trigger (debug works fine)".

Thanks for your patience!
LNU, Subhash 1 Reputation point

2022-09-28T04:25:19.563+00:00

Hi Team,

I am facing the same issue. I have my sas URI stored in a global parameter. When, I am running my pipeline in debug mode it's working fine but when I am running viw manual/scheduled trigger it doesn't work and says that the uri is missing. I have published many times the pipeline with recreating the global parameter multiple times. Could you please look into the issue?

Accepted answer

1 additional answer

Your answer

HarithaMaddi-MSFT 10,146 Reputation points

2020-09-17T09:15:13.77+00:00

Hi @markharing@bisqq.nl ,

Welcome to Microsoft Q&A Platform.

Trigger in Azure Data Factory usually uses the last published configuration for pipelines. I see that you are using master as the branch and assuming that would be collaboration branch as well. Please let me know if publishing the changes is helping to run trigger successfully.
markharing@bisqq.nl 61 Reputation points

2020-09-17T09:47:53.697+00:00

@HarithaMaddi-MSFT

I have published the lasted version to the master branch on Github and I am still facing the same issue.
HarithaMaddi-MSFT 10,146 Reputation points

2020-09-17T11:02:34.837+00:00

@markharing@bisqq.nl - This is strange. I could not reproduce this issue in my data factory. Can you please share the JSON code of the pipeline as a text file here that helps investigating it.
markharing@bisqq.nl 61 Reputation points

2020-09-17T12:34:57.393+00:00

I have attached the JSON code of the specific pipeline.25419-controle-laatste-wijziging.txt
HarithaMaddi-MSFT 10,146 Reputation points

2020-09-17T12:55:32.227+00:00

@markharing@bisqq.nl - Thanks for sharing the JSON and I tried triggering the same pipeline from my data factory and it worked fine. Since this would need more investigation, can you please send a mail to AzCommunity[at]microsoft[dot]com with Subject: "Attn:Haritha - ADF GLobal Parameters error after trigger (debug works fine)".

Thanks for your patience!
LNU, Subhash 1 Reputation point

2022-09-28T04:25:19.563+00:00

Hi Team,

I am facing the same issue. I have my sas URI stored in a global parameter. When, I am running my pipeline in debug mode it's working fine but when I am running viw manual/scheduled trigger it doesn't work and says that the uri is missing. I have published many times the pipeline with recreating the global parameter multiple times. Could you please look into the issue?

Answer 1

HarithaMaddi-MSFT 10,146

Hi @markharing@bisqq.nl ,

Thanks for sharing the details. As discussed, recreating the global parameters resolved the issue. This appears to be a publishing issue and global parameters did not get published correctly initially. As it is not reproducible easily, I discussed with Product team and a incident has been raised to investigate if it is transient issue. I will update you once the details are shared with us.

Thanks for your patience!

LNU, Subhash 1 Reputation point

2022-09-28T04:50:05.99+00:00

Hi Team,

I am facing the same issue. I have my sas URI stored in a global parameter. When, I am running my pipeline in debug mode it's working fine but when I am running viw manual/scheduled trigger it doesn't work and says that the uri is missing. I have published many times the pipeline with recreating the global parameter multiple times. Could you please look into the issue?
81244628 5 Reputation points

2024-05-03T09:52:57.1+00:00

Hi @HarithaMaddi-MSFT ,
I'm working with ADF, using global parameters, and facing the same issue. It works fine if I debug the pipeline. But, if I trigger the pipeline (manual or scheduled), it fails saying the property doesn't exist and it shows the name of the global parameter I'm trying to use. Do we not have any permanent solution to this?

I also tried recreating the global parameter but still doesn't help. Global parameter is such an important and frequently used element of ADF. I am hoping we have the solution in place. Do respond to this as soon as possible. Need the help urgently.

Answer 2

Casper Damen 1

Hey @HarithaMaddi-MSFT ,

I'm experiencing the exact same issue as described in this thread. In debug mode the pipelines run as expected, but the scheduled trigger fails because of issues in the data type of the parameters.

FYI, i'm using Terraform to deploy the Data Factory pipelines.

Kind regards,
Casper

Share via

ADF GLobal Parameters error after trigger (debug works fine)

1 additional answer

Your answer