About VikasB

VikasB

@IanAtJMP Try below APIs <#assign nameFirst = rest("/users/id/${user.id?c}/settings/name/profile.name_first").value /> <#assign nameLast = rest("/users/id/${user.id?c}/settings/name/profile.name_last").value /> Welcome ${nameFirst!""} ${nameLast!""} Hope it will resolve it.

VikasB

@akochert Sent you a PM.

VikasB

@IanAtJMP I do not think so mentioned field can be used in a sortBy clause. But these links may help you find a clue. https://community.khoros.com/t5/Developer-Discussion/Online-users-API-call-what-order-are-these-results/m-p/326055#M12791 https://community.khoros.com/t5/Developer-Discussion/Sort-labels-from-restapi/m-p/457786#M14168

VikasB · ‎04-01-2019

@CarolineS I was posting the same link here in reply 😀 Search results are returning "No results" is the expected behavior as it returns on the bases of search keyword which you are not passing in your query.

VikasB · ‎03-06-2019

@esullivan No, it was not there before. Parameters were getting added on the main search page only but not on the thread page visited via search page. This was an addition in 19.1 release. Reason to add params: Now after upgrading the community to 19.1 and search version 3.2, you can search the places as well in search results. Parameters are added to differentiate between threads/posts vs places, as per my understanding. I did not find any other specific reason to add these parameters.

Re: API V1 profile_name not working ... am I missing something?

Re: Ideation - Change Management Tips and Tricks

Re: Is there a SORT / ORDER BY clause in API V1?

Re: Viewing all content by a user within a node

Re: Is appending search parameters to URLs clicked after doing a search new?