Update ProcessReciept sample code to utilise DataStore 2.0

Bug Reports Documentation Issues
#1

Issue Description
This page’s code sample suggests saving a datastore key that logs transaction history. There is nothing wrong with this.

I’m simply suggesting to update the DataStore code to utilise the tagging feature of DataStore 2.0 so that Roblox can handle the logs for you. I’ve recieved an erasure request for a UserID, and since I’ve used this logging code, it’s a bit of a nightmare to remove the logs since the purchase IDs are pratically random.

Then again, ListKeysAsync exists, but the code should still be updated to support tagging and tag the key with the user ID.

Issue Area: DevHub Content
Page URL: MarketplaceService.ProcessReceipt

2 Likes
#2

Thanks for your report! We’ve triaged the issue and will follow up when it has been resolved.

3 Likes
#3

This change has been made! If you don’t see the changes yet, please allow some time for them to propagate.

https://developer.roblox.com/en-us/api-reference/callback/MarketplaceService/ProcessReceipt#processreceipt-callback

5 Likes
#4