In FME Form 2023.2, we used a dynamic JSON writer setup that wrote a separate file per input SQL file. Each input could have a different schema, and the setup dynamically handled this just fine using:

• fme_feature_type set from fme_basename (filename sans .sql)

• JSON writer with Schema from Schema Feature

This worked perfectly — each JSON file had its full dynamic schema.

After upgrading to FME 2025.0, only the first JSON file is written with its full schema. All subsequent files contain only the subset of fields shared with the first file. Unique fields in later inputs are silently dropped.

Example:

• A.sql has fields: ID, APR_KG

• B.sql has fields: ID, MAY_KG

Result in 2025.0:

• A.json: includes ID, APR_KG

• B.json: includes only ID — MAY_KG is missing

Nothing changed in the workspace. This appears to be a regression in how dynamic schemas are handled across multiple feature types or files in newer versions.

Can Safe confirm whether this change is intentional?