1. Create a post.
2. Run the Actiance XML export job.
3. Edit the post.
4. Run the Actiance XML export job again.
Actual: Edited post message is not included in the export.
Expected: The edited post message is included in the export.
Probably not being included because edited posts share the same CreateAt datetime as the original post and the export query is using the CreateAt timestamp in the SQL query.
Create 2 new posts, edit the last one, export
Create 2 new posts, edit the first one, export
Edit a previously exported post, export
Edit previously exported post and create a new post, export
Create a new post, edit it twice, export (should see 3 messages exported)
Tested and passed.
Added test case to release testing spreadsheet -
Thanks and ! - Can someone confirm that the resulting Actiance xml has some kind of reference in the newer edited version of a given post, that points back to the original post? If its easier, can someone attach the XML here? I might have some additional context on what the customer was expecting, and just want to understand if its covered before communitcating. They were expecting to be able to scan a file and understand the relationships between a newer version of a post, and the original.
I'm going to create a simple example export XML for you now.
Thanks … would be great to be able to share with the customer.
Ok there are some attached examples. The first export (actiance_export1.xml) includes a new post and an edit to that same post in the same export file. The second export (actiance_export2.xml) includes another edit to the post. Unfortunately the only link between the post and the edits is that they share the same DateTimeUTC value, but obviously using that value could produce false positives.