The whole path is still exported when changing the header name of an export field

When exporting items from Blackbaud CRM using an export definition users have the option to rename the header. When a user renames the header the expectation is that this is the field that will show up on the export, but it gets appended to the full path of the output item. This makes the export difficult to parse and when the exports are going straight to third party vendors it forces manual editing of export files. We would like this to work like it does when exporting an ad-hoc query: if a field gets renamed we just want to see what we renamed it. It's an explicit value that is set by the user and that's how we want it to be presented when exporting.
  • Guest
  • Jun 29 2015
  • Reviewed: Voting Open
  • Attach files
  • David Abramsky commented
    April 26, 2023 22:21

    Yes, would be super helpful if every column name could be renamed, regardless of which level of nested node the associated database field came from. It is a bother for the recipient of the exported doc to have to manually rename such long, incomprehensible (to the recipient) column names. Thank you.

  • +9