Is it Possible to Programmatically Override Activity Story LastUpdate Date on Creation?

While story types can set the LastUpdateDate, most do not. As an example, blog posts do (because they support scheduled publishing), but forum threads don't.

What type of content are you migrating that you want to adjust?

I should also mention, that I'm not tied to LastUpdateDate as a fix method. My end goal is to have the migrated posts merge more like a zipper into existing posts as if they were always a part of the story stream. If there is a better method, I'll happily take it!

Long term, this will require a bug fix to ensure that LastUpdatedDate is always set in activity stories (it defaults to "now" which is affecting the creation of stories for forum content created in the past):

A shorter-term fix may be to manually update the story LastUpdatedDates in the database to match their CreatedDate values (assuming there is a way to detect which stories are related to migrated content -- perhaps by a date range for CreateDate, for example).

Thanks Ben!

We're keeping track of content IDs for redirect purposes from the original site so I think it's possibly do able. Can you share the database tables to be looking at? (Via PM is fine if that's not something desired to be posted publicly)

The table is te_ActivityStream_Stories. The fields are going to pretty self-explanatory. You may also want to update the LastUpdatedDates on the actors--these are in te_ActivityStream_StoryActors.

For any searching later before the bug has been fixed, we ended up needing to update both the Stories and the Story Actors using a join of the table on the StoryId. Has the slight disadvantage of all of the replies being at the "same time" as the original post, but for the needs of our use case, that's an optimization we can live with rather than trying to dig into every story id to trace back to the source and then cross that with the original date/times from the source. Thanks Ben.

For any searching later before the bug has been fixed, we ended up needing to update both the Stories and the Story Actors using a join of the table on the StoryId. Has the slight disadvantage of all of the replies being at the "same time" as the original post, but for the needs of our use case, that's an optimization we can live with rather than trying to dig into every story id to trace back to the source and then cross that with the original date/times from the source. Thanks Ben.