> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Dot notation not allowed in job variable names

> Breaking change notice that job variable names can no longer contain the period character in Platform 6.

This breaking change applies to the Platform 6 feature release.

Workflow job variable names can no longer contain the period character (`.`). Workflows that violate this rule cannot be run.

### Naming format

❌ Invalid: `my.invalid.variable.name`

✅ Valid: `my_valid_variable_name`

Note that in exported workflow documents, variable names are not presented the same way as on the Workflow Canvas. The variable will include the job variable prefix `$var.job.`, which includes dot notation. In this context, a valid equivalent to the example above looks like this: `$var.job.my_valid_variable_name`.

### What should I do?

* If you have exported a workflow that includes dot notation in the job variable name, you may still import the workflow, but you will be required to change the variable name before you can run it.

* If you are upgrading your environment and there are existing workflows in the database that contain dot notation in the variable name, the upgrade may fail and throw an error. Modify the variable name to meet naming requirements before upgrading.

* If you experience any issues or need assistance, contact the [Itential Customer Support Team](https://itential.atlassian.net/servicedesk/customer/portals).

## Related reading

* Naming conventions