delimiter for the config file

[crp746rb]

I'm getting this error during a deployment with a new line in the config file.

2026-03-10T15:57:22.9002281Z ##[error]ADFT0010: Wrong path defined in config for object(path): factory.PRUSA-DW-ADF-DEV(properties.globalParameters.$$E1DataSchema.value)

the line I have in the config file is this
factory,PRUSA-DW-ADF-DEV,"$.properties.globalParameters.$$E1DataSchema.value",NAE1PDDTA

I'm guessing it is the "$$" I have in global parameter name. Is there a delimiter that I can put in front of the "$"'s or will I need to change the name of that global parameter?

[NowinskiK]

Hi @crp746rb - thanks for using the tool.
Below you can find a solution for your issue.

The Issue

When using property names with $ characters (such as $$E1DataSchema) in your Azure Data Factory global parameters, you may encounter the following error during deployment:

ADFT0010: Wrong path defined in config for object(path): factory.PRUSA-DW-ADF-DEV(properties.globalParameters.$$E1DataSchema.value)

Root Cause

The module uses Invoke-Expression to navigate to nested properties in your deployment configuration. PowerShell interprets the $ character as a special character for variable references and escaping. When your config file contains $$E1DataSchema, PowerShell sees this as an escape sequence rather than literal text, causing the path validation to fail.

The Solution

You can keep your global parameter name exactly as is — no need to rename anything. Simply escape the $ characters in your config file using PowerShell's backtick (`) escape character.

Example

Before (causes ADFT0010 error):

type,name,path,value
factory,PRUSA-DW-ADF-DEV,"$.properties.globalParameters.$$E1DataSchema.value",NAE1PDDTA

After (works correctly):

type,name,path,value
factory,PRUSA-DW-ADF-DEV,"$.properties.globalParameters.`$`$E1DataSchema.value",NAE1PDDTA

How It Works

The backticks (`) tell PowerShell to treat the immediately following $ characters as literal text rather than variable references or escape syntax. This allows the path validator to correctly process your global parameter name with special characters.

Summary

Aspect	Details
Root Cause	The $$ in your parameter name conflicts with PowerShell's $ escaping mechanism
Workaround	Add backticks before each $: Change $$E1DataSchema to `$`$E1DataSchema in your config file path
Your Parameter Name	Remains unchanged in Azure Data Factory
Your Config File	Only the path column needs the escape characters
Impact	No changes needed to your ADF resources or deployment logic

Additional Notes

• This workaround applies to any property name containing $ characters
• The backtick escape character is specific to PowerShell; no changes are needed to your Azure Data Factory definitions
• The module correctly handles the escaped path and updates the intended properties