Message Export - Extra null field appearing in Message CSV

%3CLINGO-SUB%20id%3D%22lingo-sub-969690%22%20slang%3D%22en-US%22%3EMessage%20Export%20-%20Extra%20null%20field%20appearing%20in%20Message%20CSV%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-969690%22%20slang%3D%22en-US%22%3E%3CP%3EStarting%20yesterday%2C%20we%20are%20seeing%20an%20extra%20column%20%2F%20field%20in%20the%20Messages%20CSV%20file%20-%20when%20we%20export%20messages%20from%20Yammer%20(via%20UI%20or%20via%20the%20Export%20API).%26nbsp%3B%20According%20to%20documentation%2C%20the%26nbsp%3B%3CSTRONG%3Emessage_type%3C%2FSTRONG%3E%20column%20should%20be%20the%20last%20in%20each%20row.%26nbsp%3B%20We%20are%20seeing%20that%20is%20the%20case%20for%20the%20header%20row%2C%20but%20each%20subsequent%20message%20row%20entry%20in%20this%20CSV%20file%20has%20an%20additional%20blank%2Fnull%20entry.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAgain%2C%20this%20just%20started%20occurring%20yesterday%20(Oct%2030).%26nbsp%3B%20There%20is%20no%20indication%20in%20the%20documentation%20(%3CA%20href%3D%22https%3A%2F%2Fdeveloper.yammer.com%2Fdocs%2Fdata-export-api%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fdeveloper.yammer.com%2Fdocs%2Fdata-export-api%3C%2FA%3E)%20nor%20in%20the%20updates%20blog%20indicating%20a%20change.%26nbsp%3B%20Hoping%20someone%20from%20Microsoft%20can%20comment%20on%20this%20-%20in%20terms%20of%20whether%20this%20is%20expected%20now%20or%20if%20this%20was%20an%20issue%20(and%20if%20so%20when%20it%20will%20be%20resolved).%26nbsp%3B%20Assume%20it%20is%20an%20issue%20since%20there%20is%20no%20column%20header%20mapped%20to%20this%20additional%20null%20field%20value.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-969690%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAPI%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eexport%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EREST%20API%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYammer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Visitor

Starting yesterday, we are seeing an extra column / field in the Messages CSV file - when we export messages from Yammer (via UI or via the Export API).  According to documentation, the message_type column should be the last in each row.  We are seeing that is the case for the header row, but each subsequent message row entry in this CSV file has an additional blank/null entry.

 

Again, this just started occurring yesterday (Oct 30).  There is no indication in the documentation (https://developer.yammer.com/docs/data-export-api) nor in the updates blog indicating a change.  Hoping someone from Microsoft can comment on this - in terms of whether this is expected now or if this was an issue (and if so when it will be resolved).  Assume it is an issue since there is no column header mapped to this additional null field value.

0 Replies