I'm not precisely sure if you can do that, but then again, I'm not a Developer either so I could be wrong.

Perhaps some kind of programatic change to the XML after you receive it might solve the problem, pivoting off of the date parameter:

http://lithosphere.lithium.com/t5/Growing-Successful-Communities/Understanding-REST-API-query-string-parameters/ta-p/8721

Or perhaps you can tinker with the sort order parameter:

http://lithosphere.lithium.com/t5/Growing-Successful-Communities/Understanding-linear-and-threaded-sorting-in-REST-API/ta-p/7151

http://lithosphere.lithium.com/t5/Growing-Successful-Communities/REST-API-Problem-to-sort-messages/m-p/6415#M2006

but I'm not sure if any of those solutions would really work. Sorry if none of this is helpful.

If I understand correctly, you want to get a list of floated threads sorted by the date of the root post. In your sample code, it looks like you're sorting messages within a thread, rather than sorting the list of threads.

Here's a quick example of sorting the list of floated threads (community-wide) by the date of the root post (most recent first):

<#assign floated_threads = rest("/subscriptions/global/float/thread").subscriptions />
<#list floated_threads.subscription?sort_by(["target","messages","topic","post_time"])?reverse as subscription>
${subscription.target.messages.topic.id} - ${subscription.target.messages.topic.post_time} <br>
</#list>

 So basically I get the list of floated threads across the entire community, iterate through the list sorted in reverse order by post_time, and then output the id and date of the root post.

I want to point out that in this case the sort_by is taking a sequence of 4 values which correspond to the names of the nested subvariables. For example, the post_time of the root post as I'm looping through the subscriptions is accessible via "subscription.target.messages.topic.id", so my parameter for "sort_by" is the sequence "["target","messages","topic","post_time"]"

I hope this helps!

darrenSP - You can easily update the confirmation message from a text editor. 

Below is the text key used for show Thanks for your feedback message. 

page.RatingEnumerationDisplay.feedback.success.title

Studio -> Text Editor -> Community Text 

Lithium uses the text key for each string appearing in the community.  You can search for the string you want to update from there. 

https://community.lithium.com/t5/FAQs-email-templates-and-text/About-text-keys/ta-p/109029

https://community.lithium.com/t5/FAQs-email-templates-and-text/Find-text-keys/ta-p/109027

Regarding the custom component for this, there is no POST API call available for helpfulness, you can only perform GET action. 

https://community.lithium.com/t5/Developer-Documentation/bd-p/dev-doc-portal?section=commv2&collection=tkb_helpfulness_ratings#constraints-message.id

The top of the document mentioned that the features are added in 15.1. Make sure your community have upgraded to 15.1.

But for the use case mentioned, you should be able to do something like this in previous versions:

SELECT * FROM messages where category.id = '<category>' and depth=0 ORDER BY post_time DESC

Hope this helps.

Hi Inactive User ,

https://developer.khoros.com/khoroscommunitydevdocs/docs/linear-and-threaded-sorting 

The above article: has the following context

/restapi/vc/threads/id/6415/messages/linear?message_viewer.message_sort_order=thread_ascending

 Please Give Kudos if you find this post useful and mark this as Accepted Solution if this is the required solution.

Hi,

is it not that you have not set a sort order on depth and so the call is assuming your passing a sort order of DEFAULT which is invalid.

should it not be:

SELECT id, short_title, view_href, depth, position FROM categories WHERE depth <= 2 AND id IN('<catid_1>', '<catid_2>', '<catid_n>') ORDER BY depth DESC, position ASC

?