Skip to main content

Posting on behalf of a customer. 
Currently when you add a new field to a fetch in rules and export that fetch to S3, any new fields that you might’ve added aren’t appended to the end of the S3 export.

For example if you have a field listing like this in the rule fetch:

Name, created date, Segment

When you add a new field to that fetch like this:

Name, created date, Segment, Country

The ideal result would be that the S3 export would show up like above. However, currently it shows up something similar to this in the resulting CSV.

created date, Country, Name, Segment

The request is that the fetch config column sequence would dictate the export column sequence.

@Justin Bills sorry for the inconvenience. Sorry for the delay here. I will check on this and get back to you.

This appears to export in alphanumeric sort, is that correct @rakesh ?

Yes, Dan.

Hello @dan_ahrens  and @rakesh  That’s not how any of our files are being received.  There doesn’t seem to be any rhyme or reason as to where the data columns are.

Ex.  I attempted to add “Modified_date” to the export.  It landed between a field that starts with P and another that starts with C.   And that was in the middle of the export file.  The file leads with M and ends with a g.  

If it’s supposed to be alpha numeric, is it off the out put header, or out put field label?  Also, is there any character that could cause this to break?  For example, our data is expressed with underscores on the label.

Terms & ConditionsCookie settingsAccessibility statement