Using LiQL or SQL on Aurora instead of GraphQL?
We had an LiQL query we were using for years to surface community posts on our help center, and following the move to Aurora we need to update this to GraphQL. However, the developers on that team would prefer SQL/LiQL as their system is not set up for GraphQL. Is it possible to still use LiQL or SQL queries while on Aurora?
Not receiving user email addresses from search endpoint
I have a script that queries the search endpoint for information about Khoros users. The API call looks roughly like /api/2.0/search?q=SELECT id, email FROM users LIMIT 10 When developing this script against one Khoros installation, I found that the Khoros user associated with the API request needed to have several "User Management" permissions granted to it in order to receive email addresses via this API call. (In particular, granting "View user reports in Admin Metrics", "Manage roles, user bans, and abuse notifications in admin and user profiles", and "Manage roles in user profiles" seemed to be sufficient.) However, when running this script against a second Khoros installation, I am not receiving back any email addresses. Every single user returned has the empty string as their email address, and I've tried querying several hundred (all of whom should have emails). For instance, a response may look similar to the below (redacted) sample: { "status": "success", "message": "", "http_code": 200, "data": { "type": "users", "list_item_type": "user", "size": 10, "items": [ { "type": "user", "id": "1000000", "email": "" }, ...additional users removed for brevity... ], "next_cursor": "AbCdEf" }, "metadata": {} } I have double-checked the roles and permissions for the Khoros user I'm using for this API request. What's the best way to debug? What are some other reasons that I may not be receiving any email addresses?
Unable to retrieve users using v2 API
Unable to retrieve users from /api/2.0/search?q=SELECT * FROM users endpoint though it's returning 200 response. What could be the reason? Here is the response: { "status": "success", "message": "", "http_code": 200, "data": { "type": "users", "list_item_type": "user", "size": 0, "items": [] }, "metadata": {} }Online User Count is Completely Wrong
I'm trying to get an accurate count of online users and it's quite obvious the count is completely wrong just by looking at the results I'm encountering on my staging environment. The LIQL query used is fairly simple: SELECT count(*) FROM users WHERE online_status='online' Given the number of people who access our staging server, I would expect the result of this to be a low single digit number. Instead, I got a result of over 30 users. So I dug into the API results: SELECT login,last_visit_time FROM users WHERE online_status='online' The results list users with last visit times from 2020 and 2021 as well as users from earlier in 2022 that I know for a fact aren't online. How is Khoros defining an "online user" here? Is the behavior I'm seeing a bug or expected behavior?Possible? Display 30-day FRT on a Board Component?
Our Board Oversight teams would like a component on their boards that displays the First Response Time (FRT) average over the past 30 days. While I realize I can grab this in Community Analytics, and I also am comfortable around the API... I'm a bit of a newbie when it comes to grabbing time-constrained data via the API Here's the board component with the line in question: <#if userHasApplicableRole> <#assign frt = [30_DAY_BOARD_FRT_AVG] /> <#-- this --> <div class="dc-boardwidget-FRT" title="FRT 30-day average"> <i class="fa-regular fa-reply-clock"></i> <span>${frt}</span> </div> </#if> Is this possible with the API? wkd-oliverHow to get only Messages where some specific custom field have value?
Hi Team, I have a custom field added by Khoros in the messages object, I want toget only Messages where that specific custom field has value. Sample query: select c_abcd from messages where c_abcd!="" I don't want to get all messages and then in the loop filter the messages which don't have any value. Is there any direct API or solution to get the messages where thec_abcdcustom field has some value? Any related replies would be appreciated. Regards AmanAPI v2 Search doesn't work
Reading this page, I quote: "In v2, perform a one-or-more term search with a comma-separated list of terms wrapped in parentheses. Use this when you want to return messages that have at least one of these terms in the defined fields. WHERE subject MATCHES ('apples', 'bananas', 'cherries')" This query returns 2 results: select subject,body from messages where subject matches 'attachment' This query returns 0 results. select subject,body from messages where subject matches ('attachment','android') According to the documentation I should be getting results. Fair to say that it's not WAI?Data/Metrics on Subscriptions
Hi there, I got a question that I thought would be straight-forward, but doesn't seem to be: "how many users are subscribed to category XYZ?" Apparently there's no good way to answer this? In looking through the documentation and forum, all I was able to find was this documentation here: https://developer.khoros.com/khoroscommunitydevdocs/docs/get-a-count-or-list-of-users-subscribed-to-a-board?_ga=2.165259263.1583072279.1692296336-111620096.1668529588 This is using a) the outdated v1 of the API and b) only returns counts for boards, blogs, or Groups. What about Group Hubs and Categories? Is there really no way to get a list of everyone who's subscribed to a particular Category? Thanks for any help!Handling the upcoming LIMIT and OFFSET changes
You might be aware of the upcoming changes to LIMIT and OFFSET having a maximum value of 1000 in 23.12. Obviously this is likely to cause a problem to any custom components that loop through data such as messages. Cursor will work fine in some scenarios, but any kind of custom pagination will need UI/UX work to access records greater than 2000! Using cursor we'd only be able to move forward and not skip to page 1000 for example. Any other thoughts on how this could be achieved with CURSOR?!
