Azure Data Factory - Error creating a parameterised mapping dataflow

Question

I am having an error when trying to create a parameterised Mapping Data Flow. More specifically, I have the following error. Anyone have suggestions on how to fix it or what the error may be?

{ "Message": "ErrorCode=InvalidTemplate, ErrorMessage=Unable to parse expression 'body('DataFlowDebugExpressionResolver')?.Data Vault Loadb734571b6d5a414ea8387a08077f1ff1?.DataVaultSource.sourcetable': expected token 'EndOfData' and actual 'Identifier'." } - RunId: 24ee9884-610d-4061-a9be-670aeb8f1660

Thanks @Leon and @Joel for your responses. I am attaching my pipelines here for your consideration

[ Data Source connection with Parameter. I can preview data with no errors 1

What is the Data Flow parameter type? Pipelines do not support the same variable types, I believe I've seen this before when passing mismatched parameter types. — Joel Cochran
– Joel Cochran, Commented May 11, 2020 at 14:07

Sarath · Accepted Answer · 2020-05-12 06:34:39Z

16

I have found the resolution to the problem I raised yesterday. The error was caused by the name of the Mapping Data Flow (Data Vault Load).

I raised a request from Microsoft and they had the following suggestion

Spaces in name of object and parameters does not go well

Once I removed the spaces in my Mapping Data Flow name it, this particular error was resolved.

Thanks to everyone that responded.

answered May 12, 2020 at 6:34

Sarath

2512 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Abhi Over a year ago

Worked for me. Indeed I removed the space from the name of my 'Data Flow'

Jeremy Caney · Accepted Answer · 2023-07-31 00:53:10Z

1

Whenever you use a parameterized data set to remove the space from the dataflow name, like this from "dataflow test"

enter image description here

to "dataflowtest"

enter image description here

Because when you make use of the parameterized dataset, it shows up in the Settings tab, not in the Parameter tab correctly. I mean, it is just my theory, but it takes its own name according to the dataflow name rule, which is this:

enter image description here

So when you remove the spaces from your dataflow name, it will work—trust me, because its works for me. As you can see in the below image, I have a lot of parameterized data sets and it's a live project:

enter image description here

I was getting this error, which was absurd:

enter image description here

After removing the space, though, we are getting our data:

enter image description here

So there is no need to create a separate data flow from scratch; if you create the dataflow from scratch you will face the same issue which, will be this space one.

edited Jul 31, 2023 at 0:53

Jeremy Caney

7,818115 gold badges58 silver badges86 bronze badges

answered Jul 19, 2023 at 9:57

Yogesh Prasad

111 bronze badge

1 Comment

Eric Aya Over a year ago

enter image description here is a placeholder you are supposed to replace with an actual description.

Mohamed Elkholy · Accepted Answer · 2021-12-17 15:51:37Z

0

I have been looking for going around looking for this answer it is 2021 and Microsoft still didn't add any validation or restriction for the naming of the Data Flow

answered Dec 17, 2021 at 15:51

Mohamed Elkholy

111 silver badge2 bronze badges

Collectives™ on Stack Overflow

Azure Data Factory - Error creating a parameterised mapping dataflow

3 Answers 3

1 Comment

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related