Skip to content

Case sensitive field names cause errors in lots of contexts. #1019

@acrosman

Description

@acrosman

Currently if you have two fields with the same name, but with different cases, they will be listed in output as different fields. But most output targets don't accept that as valid output.

Minimal Example:

- object: Account
  fields:
      Name:  Company One
- object: Account
  fields:
     name: Company two

There are places in more complex use cases where this pattern applies and it's an easy mistake to me.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions