allensmith81
Boss
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: QraphQL Missing constraint on the messages collection
If you could, it seems a bit daft that I either need to chunk the data into small enough firsts so I don't pull more records that necessary or that i have to process the data in our external cloud system and evaluate it for post time on my side. It also doesn't make sense that i can constrain upon conversation activity post time but not the original post time itself.QraphQL Missing constraint on the messages collection
Hi all, I am trying to create a system to pull all messages from a board posted in the last hour, can someone tell me what I am missing here.. There is no constraint for postTime.. I only want the new posts (depth 0) but that makes both of the other constrains useless as the feed would be polluted with messages surfaced because someone has commented on the original post...Re: Creating a blog on behalf of another user - GraphQL
AdamN Thanks I already know of this way - having been using the API since we moved Skype to the platform in 2010 - I am very experienced at APIs and breaking the platform in ways it was never supposed to be :P I would still like to see an API call I can make without the extra trip through the login flow to create a blog post on behalf of another user. A north star would be it's possible for a community member to create 'delegated' authors for any blog they are permissioned to write and the delegated user could then create a post and select the author from a drop down list of users they are 'delegate' for. Maybe with some sort of 6 monthly automatic review requiring the user who granted the delegated permissions to confirm they wish them to continue.Creating a blog on behalf of another user - GraphQL
Hi all, In classic we could create a blog on behalf of another user if the API user creating the blog had the permission to switch user. This was achieved using a APIv1 call the message endpoint and passing in the parameter message.author=id/<userid> in the api call. As far as I know this was not included in APIv2 and I can't find it in graphAPI and its a very crucial function for us until LarryI adds Ghost Writing to the platform! I have tried everything I can think of and it won't let me do this.GraphQL Mutation for Creating a blog | No author parameter
Hi all, Unless I am going made, there is no option in graphQL to create a blog on behalf of another user is there? i.e. in the input field something like "Author": { "user" : {"id": "user:1234"}} This would be incredibly helpful as we use the APIv1 / v2 calls today to create a draft blog on behalf of a user so we can send those draft links to another user to enable Ghost writing. Example: A team needs to public a blog, however for consistency the team publishes all its public announcements from the director of engineering. The assistant (or another delegated user) needs to write a blog and make it appear as though it was from the directory himself.Analytics API: nodeSubscriptions unexpected behaviour
Hi all, I am using the Analytics API and I am trying to get a total count of subscriptions to all nodes of the community. If I sent the following query to graphQL, I always get a null value: nodeSubscriptions(constraints: {startTime: $startTime, endTime: $endTime}) { metric { value } } } Variables used are: (Yes I know its 3 months!) { "startTime": 1719792000000, "endTime" : 1727740799000 } However if I make this call nodeSubscriptions(constraints: {startTime: $startTime, endTime: $endTime, conversationStyle: FORUM}) { metric { value } } } I successfully get a count of subscriptions, is this bug? or has nodeSubscriptions actually been disabled from pulling a count of the node subscriptions across the community? Even if you had to specify conversationStyles for this call that wouldn't let you know how many subscriptions had been made to the category level. There is a nodeType of Category / GroupHub but that doesn't seem to do it either.Re: Khoros Communities: Aurora 24.12 Release Notes
sloth2073 Excellent, its not in our staging - a support engineer said they could get it working but as we demonstrated to them, even if we do the exact same thing they did.. on posting the background colors etc all get blown out. Not sure if its a migration to aurora issue or something unique about our instance but something isn't 'as expected' for us.
