Set ForumThread LastUpdatedDate via Automation Studio (core_v2_forumThread API)?

Apologies if this question is duplicative but my search-foo has failed me. Is there a way to either explicitly set the Last Updated Date (so as to not trigger Activity Story or user Unread status) of a forum thread when updating the thread type via API or suppress the Activity Story and Unread Status change from an automation event?

Situation: Trying to do essentially the opposite of this:  Option to Convert Questions into Discussions where we have forums that have predated the existence of Question/Answer format and we'd like to convert them to using the Q&A format so we can better keep track of threads that need attention or a definitive answer. (Scale is hundreds to thousands so individually opening each one and clicking is a rather unattractive workaround)

Using the API in Automation studio, I can successfully get the list of the threads, use the forumThread.Update method to change the type (and even ensure the post date stays the same) but in testing it is flagging everything as unread for users and is surfacing activity stories based on the update date (time I trigger the Automation).

It feels similar to TE-17806 mentioned here in REST context:  Is it Possible to Programmatically Override Activity Story LastUpdate Date on Creation? but I don't see a documented method for setting the LastUpdatedDate within the core_v2_forumThread.Update API

If this is something best done at the database level, that's an option, but one that I was hoping to avoid if possible.

Parents Reply
  • Good thought, but that endpoint (the second for Automations/Widgets) is to be able to mark as read for a specific user a piece of content as I understand it. That would require tracking all of the users' current read status prior to the change, doing the update to change the type, and then reset the status to the correct status for each user. I don't think that is feasible to do from a velocity script in an automation on thousands of threads for tens of thousands of users.

    The API call I'm using to do the change from Discussion to Q&A is core_v2_forumThread Script API Update Overload 2. It would be awesome if there were some heretofore/previously undocumented feature that let that run without changing the read status of the thread.

Children
  • That would require tracking all of the users' current read status prior to the change, doing the update to change the type, and then reset the status to the correct status for each user. I don't think that is feasible to do from a velocity script in an automation on thousands of threads for tens of thousands of users.

    Good point. That's what I was thinking with that comment, but I wasn't sure about how feasible it would be. I added the edit in my comment which linked to the same page as you shared. Might be good to add to  Ideas and Improvements but other than that, I'm out of ideas. If I come across anything, I'll update this thread.

    Hopefully someone else can add some suggestions!