Rename

Rename lets you relabel incoming files or sheets so downstream transforms, validations, and delivery targets can reference them by a consistent, predictable name — regardless of what the source system called them.

Availability: GA

What it does

Input: files or lists.
Output: the same files or lists, with new names applied according to your rename mappings. File contents are unchanged.

When to use it

A source system sends files with inconsistent or unpredictable names (for example, a timestamp in the file name) and you need a stable name downstream.
You want to align sheet names across sources before using Combine sheets by row or Join sheets by column.
A delivery target expects a specific file name.

How to configure it

In the MFF builder, add a Rename node after the node that produces the files or lists you want to rename.

Settings

Setting	Description	Default
Renames	A list of old name → new name mappings. Add one entry per file or sheet you want to rename; anything not listed passes through with its original name.	Empty list

Example

Input

A file named export_2024_05_01.csv.

Output

The same file, renamed to orders.csv, using a rename mapping of export_2024_05_01.csv → orders.csv.

Troubleshooting

The rename didn't apply

Check that the old name in your mapping exactly matches the incoming file or sheet name, including case and file extension.

Names change from run to run

If the source file name is dynamic (for example, includes a date), use a pattern-based match if available, or add a rename entry for each expected variant.