You're correct: there's currently no API to query users by owned item (defId). All UserItems read operations are scoped to a single user. We've noted this as a feature request. In the meantime, rather than adding storage logic to every purchase flow, you can attach a Post API Hook to the item award/purchase/drop operations. The hook script maintains an index for you (e.g. flags in summary friend data searchable via FindUsersByUserSummary).
administrators
Private
Posts
-
User Inventory Search -
Leaderboard settings missing?The production app most likely has "Show Game Design Features" switched off. It's a per-app setting under
Advanced Settings -
Need a lastLoginUpdate function.Could you share what you're using last-login time for (e.g. dormant-user cleanup, segments, promotions)? Last login drives several systems, including dormant-user identification and login analytics, so setting it without a real login would affect more than the display. If we know the goal, we can recommend (or consider) a more targeted option, such as tracking a separate activity timestamp or excluding those users from dormancy.
-
[Bug Report] Builder API deploy copies CustomEntities despite preservation being enabledThe fix for this has been deployed... (a couple weeks ago actually - apologies for the lagging notice!)
-
Bulk import / API for registering in-app productsWe also strongly suggest using the ProductManagement service through a Cloud Code script to create and manage products programmatically, rather than entering them manually in the Portal. This can help automate catalog setup and make it easier to maintain product definitions in your own workflow. Please see the documentation here: https://docs.braincloudservers.com/api/capi/productmanagement/
-
Bulk import / API for registering in-app productsThanks for the suggestion. I’ll forward this feature request to our team for review. In the meantime, depending on your use case, you may be able to reduce the number of store product IDs you need to manage by using
CachePurchasePayloadContext(), introduced in brainCloud 5.8: https://updates.braincloudservers.com/?query=CachePurchasePayloadContext. It lets you cache additional purchase context before the transaction so brainCloud can combine it with the receipt during verification, potentially allowing product IDs to be reused across different items, offers, or price points. -
[Bug Report] Builder API deploy copies CustomEntities despite preservation being enabledHmm - I'll get the team to take a look at it.
-
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1We've deployed the patch for this. Apologies for the delay!
-
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1Okay - it looks like that script may be callable via cloud code script in S2S - but not via the S2S api directly... The devs are looking into it.
-
SYS_UPDATE_CAMPAIGN_JSON (Campaign S2S) returns "Unrecognized request" even though our app is already running 6.0.1Hi guys,
Can you still get this error? We can't repro it?
Paul.
