Corey

I can confirm the extra "parse" was indeed the username (I changed the username to see if dashboard display changed).

I meant username…

No, the username doesn’t show up in the configuration I mentioned, so there seems to be a bug

I think the benefits of `ParseBytes` are highlighted in the link you already shared: https://community.parseplatform.org/t/saving-byte-data-to-parseobject/1804 My guess would be `Bytes` was simply overlooked by the other SDKs, Dashboard, and docs...

> I see, so it shows just the raw JSON data, like a custom data type - neat. @mtrezza I believe there are additional benefits as the data is stored...

Implementing this into Schema for the JS SDK would require looking here: https://github.com/parse-community/Parse-SDK-JS/blob/8115e959533d1676fe5e5551bc81888b21fc12ef/src/ParseSchema.js#L18-L30 The Swift SDK counterpart is [here](https://github.com/parse-community/Parse-Swift/blob/4ccb8a6222c1c5607a328c6be64932b47191e3fb/Sources/ParseSwift/Types/ParseField.swift#L18-L46): ```swift /// Field types available in `ParseSchema`. public enum FieldType: String,...

`Bytes` has been in the Objective-C SDK for years. The SDK can [encode](https://github.com/parse-community/Parse-SDK-iOS-OSX/blob/2e4242c683e645a7d78ff37dd34398119178c0c5/Parse/Parse/PFEncoder.m#L36-L43) and [decode](https://github.com/parse-community/Parse-SDK-iOS-OSX/blob/386f659fb7c20c78d4adf386f3978fed8c9c2293/Parse/Parse/PFDecoder.m#L43-L55) Bytes.

If my memory serves me correct, the JS SDK has only been more complete than the Objective-C and Android SDK's in recent years due to open-source maintainers beefing it up...

Currently, the server isn't designed to handle this and the Client SDKs are expected to strip anonymous when linking: Objective-C SDK: https://github.com/parse-community/Parse-SDK-iOS-OSX/blob/2e4242c683e645a7d78ff37dd34398119178c0c5/Parse/Parse/PFUser.m#L862-L884 Parse-Swift SDK: https://github.com/parse-community/Parse-Swift/blob/1636285beb51d9bf33230d5f80a9db5f8ec8707c/Sources/ParseSwift/Authentication/Protocols/ParseAuthentication.swift#L432-L486 Android SDK: https://github.com/parse-community/Parse-SDK-Android/blob/ea2a6a7d7b761a568dfb261cd0694699f3c5a978/parse/src/main/java/com/parse/ParseUser.java#L1212-L1222 I think...

> REST API routes /events are implemented but there is no built-in (default) analytics adapter that would store analytics data in the DB. I'm not aware that anyone is providing...