517: Additional paremter Options not allowed for GlobalDataStore SetAsync() Call | OrderedDataStore bug

Bug Reports Engine Bugs
#1

Reproduction Steps

Direct Links
Infectious Smile Testing - RobloxInfectious Smile Testing - Roblox
I doubt this is an isolated issue due to multiple recent unsolved devforum topics about this matter
OrderedDataStore SetAsync additional parameter options not allowed error
[UNSOLVED] Additional parameter UserIds not allowed - ordered data store

System Information:
AMD Ryzen 7 5800H with Radeon Graphics
16GB RAM
NVIDIA GeForce RTX 3060 Laptop GPU
(I highly doubt this is a local system issue as this is a roblox server bug)

optionsdatastoreissue.rbxl (35.9 KB)


Expected Behavior

I expect the metadata in the DataStoreSetOptions instance to be passed into :SetAsync() properly, and then be able to receive that metadata upon calling :GetAsync()

Actual Behavior

When I call :SetAsync() on the GlobalDataStore, I get this warning no matter how I modify the passed in DataStoreSetOptions


Workaround

No workaround

Issue Area: Engine
Issue Type: Other
Impact: Very High
Frequency: Constantly
Date First Experienced: 2022-06-26 02:06:00 (-05:00)
Date Last Experienced: 2022-06-27 00:06:00 (-05:00)

3 Likes
#2

All of these topics are about OrderedDatastores, is your datastore an OrderedDatastore as if so, OrderedDatastores currently do not have Datastore 2.0 implemented which is why these parameters do not function. (Unless this was changed incredibly recently)

1 Like
#3

This feature would be beyond useful and the absence of it is currently prohibiting me from making some very key features for my game!

1 Like
#4

Yep, this is an OrderedDatastore. Forgot to mention that.

1 Like
#5

GetOrderedDataStore doesn’t have the features of DataStores V2. Note that you can’t pass in an options on the GetOrderedDataStore call: DataStoreService | Roblox Creator Documentation

Therefore, you can’t use the DataStores V2 features on OrderedDataStores, and this is not a bug. You should file a feature request instead.

2 Likes
#6

If so, there has been a regression in the documentation on such missing feature, the page used to mention the fact that datastore 2.0 was not implemented on ordered datastores. Since, that warning was removed and replaced with a warning saying that datastore versioning is not available on ordered datastores.

1 Like
#7