58 results found

1. Termination protection for realm apps

   it is very easy to delete a realm app, once deleted we cannot restore the app or recreate with same appId in this case we will be forced to publish new versions of apps with new app IDs. also there are no access roles when it comes to app services which is a big security hazard for apps in production as any member can delete an app by mistake.
   My Ideas are:
   1. Introduce role based access for app services
   2. give a restore app option for deleted apps (30 days before permanently getting deleted)

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Support network proxy for Realm SDKs

   I copy here the feedback received on a support case about the lack of network proxy support in the Realm SDKs. That feature might be of interest for other customers as well, particularly during a product development phase, when we are mainly working behind a corporate proxy.

   "We deeply regret the inconvenience caused by the absence of proxy support in our SKDs at this time.

   But, We have received an update from our production manager regarding the ==tentative plans== to address the APIs related to proxy settings for all of Realm software development kits (SDKs) in the upcoming quarters, specifically Q3 and Q4."

   I copy here the feedback received on a support case about the lack of network proxy support in the Realm SDKs. That feature might be of interest for other customers as well, particularly during a product development phase, when we are mainly working behind a corporate proxy.

   "We deeply regret the inconvenience caused by the absence of proxy support in our SKDs at this time.

   But, We have received an update from our production manager regarding the ==tentative plans== to address the APIs related to proxy settings for all of Realm software development kits (SDKs) in the upcoming quarters, specifically… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Realm (General)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Use Enums in Generated Realm Object Models

   When the JSON Schema for a collection contains a string enumeration, like the following:

   {
     "properties": {
       "_id": {
         "bsonType": "objectId"
       },
       "enumExample": {
         "bsonType": "string",
         "enum": [
           "Foo",
           "Bar",
           "Baz"
         ],
         "title": "The type of entity that was favorited, such as a Workout."
       }
     },
     "required": [
       "_id",
       "enumExample"
     ],
     "title": "EnumExample"
   }
   

   ... the generated Realm Object Models don't take advantage of the limited possible values. I've generated all of the available languages, and they all generate variations of a simple string.

   Here's TypeScript as an example:

   import Realm from "realm";
   export type EnumExample = {
     _id: Realm.BSON.ObjectId;
     enumExample: string;
   };
   export const EnumExampleSchema = {
     name: 'EnumExample',
     properties: {
       _id: 'objectId',
       enumExample: 'string'
     },
     primaryKey: '_id',
   };
   

   Ideally, the generated type would be narrowed. Even more ideal would be enforcement of that at runtime, but I'm less knowledgeable about how that could work!

   import Realm from "realm";
   export type EnumExample = {
     _id: Realm.BSON.ObjectId;
     enumExample: "Foo" | "Bar" | "Baz"; // <--- this is the only line that changed
   };
   export const EnumExampleSchema = {
     name: 'EnumExample',
     properties: {
       _id: 'objectId',
       enumExample: 'string'
     },
     primaryKey: '_id',
   };
   

   When the JSON Schema for a collection contains a string enumeration, like the following:

   {
     "properties": {
       "_id": {
         "bsonType": "objectId"
       },
       "enumExample": {
         "bsonType": "string",
         "enum": [
           "Foo",
           "Bar",
           "Baz"
         ],
         "title": "The type of entity that was favorited, such as a Workout."
       }
     },
     "required": [
       "_id",
       "enumExample"
     ],
     "title": "EnumExample"
   }
   

   ... the generated Realm Object Models don't take advantage of the limited possible values. I've generated all of the available languages, and they all generate variations of a simple string.

   Here's TypeScript as an example:

   import Realm from "realm";
   export type EnumExample = {
     _id:

   … more
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Realm Query Language Documentation: Sort, Distinct, Limit

   Realm Query Language Documentation located here https://www.mongodb.com/docs/realm/realm-query-language/#sort--distinct---limit needs updating with more specific examples of how to implement SORT, DISTINCT and LIMIT. The documentation also appears to be out of date (?)

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Automatic Syncing of Referenced Objects

   Please implement the feature to automatically sync referenced objects when you add a subscription to the parent object. This would mitigate the need for multilayer subscriptions at every step.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Documentation for the path parameter of Configuration

   The path parameter on the Configuration seems to be an important parameter when it comes to sync. This value should not be set when using sync. See the link to a forum post for more information.

   Overall, the configuration parameters could use some documentation.

   https://www.mongodb.com/community/forums/t/realm-at-path-already-opened-with-different-sync-user/165579/8?u=chris_lawrence

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Increased Authentication Visibility and Better Customization

   Having a fully managed authentication through Realm has been great, it continues to save a lot of time developing authentication and security protocols. With that said, as my application's admin I feel like my visibility into authentication is sparse. I can not help my users when they run into issues and am concerned as our application continues to grow. My request is for more visibility into authentication, including, but not limited to the following...

   • Last Login Date: Ability to run queries on this field in order to generate daily, weekly, and monthly user metrics, most importantly the number of logins in order to track growth, retention, etc. We would also like to be able to run similar queries on Created Date and Providers. We can download 3rd party packages to try to manage this but the data is already here.
   • New Account (email and others): More visibility in terms of when a new user signs up and how long it takes MongoDB to send an email to a new user for sign up. We continually get feedback that the email randomly takes too long to send and have no way of managing or knowing the scope of this. The same goes for forgotten passwords. Similar to the first comment we want to be able to generate some sort of reports to understand this better ** We know that you can look at Logs but they are sparse and we are uncertain what the runtime is actually telling us **
   • Email Customization: Our users expect our email/forgotten password emails to be professional and the template we are sending currently does not allow customization. This leads to mistrust (receiving an email from MongoDB vs. our company). We are concerned it impacts growth. The image I have attached for password reset is what our users receive.

   Cheers!

   Having a fully managed authentication through Realm has been great, it continues to save a lot of time developing authentication and security protocols. With that said, as my application's admin I feel like my visibility into authentication is sparse. I can not help my users when they run into issues and am concerned as our application continues to grow. My request is for more visibility into authentication, including, but not limited to the following...

   • Last Login Date: Ability to run queries on this field in order to generate daily, weekly, and monthly user metrics, most importantly the number of logins… more

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. encryption

   A better encryption key rotation without write copy

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Return count of inserted/updated records for BulkWrite and collection.insertMany( with duplicates)

   On success, BulkWrite returns a null response as mentioned in the documentation - https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/#collection.bulkwrite--. Can you please send correct response details ( no. of records inserted, no. of records updated ) ? The functionality works correctly but we need correct details returned for debugging issues instead of making a redundant find call to check the results.

   When inserting with duplicates, mongo inserts unique records successfully and discards duplicates. However, in the response sent, it does not specify the number of successfully inserted records and the count of duplicates, whereas, this information is returned in normal mongo SDK insert

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. transfer authenticated user to another project

    im surprised that nobody asked about this. firebase already have this functionality whereby i could export existing firebase firestore and authenticated users to another project.

    in mongodb realm, collection and functionality can be export and imported. but existing authenticated users are not able to move. or maybe im missing something. i find this a big bummer when duplicating project for staging or testing or even for another client. i dont wish to need to do custom authentication todo this, but i am on the way todo it.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Track every Realm App's secret change in Deployment History

    Currently, only deployed changes in Realm App are tracked in Deployment History and can be re-deployed but not secret changes. In the situation, if we deploy the change in Realm App new record is created in Deployment History with existing Secret with the current value 'v1', after that let's say we updated the same Realm's secret twice (with values 'v2' and after some time with 'v3'), such changes are not tracked, no new records in Deployment History. If we re-deploy last created record in Deployment History, it will also overwrite Secret's value from 'v3' to the old one 'v1'. Tracking every Realm App's secret change in Deployment History (or in a dedicated for secrets history section) could help to keep better control on secret's values.

    Currently, only deployed changes in Realm App are tracked in Deployment History and can be re-deployed but not secret changes. In the situation, if we deploy the change in Realm App new record is created in Deployment History with existing Secret with the current value 'v1', after that let's say we updated the same Realm's secret twice (with values 'v2' and after some time with 'v3'), such changes are not tracked, no new records in Deployment History. If we re-deploy last created record in Deployment History, it will also overwrite Secret's value from 'v3' to the old one 'v1'. Tracking… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Deep Copying Objects Across Realms (aka: Partitions)

    Please have the SDKs allow to copy objects from one partition to another. Currently you have to manually do it, which isn't great but not horrible, until your object has nested Objects, List<>s or EmbeddedObjects (via referenced 'foreign_key' / _id) - that is when it gets nasty and cumbersome. In Legacy Realm when ever you copied a top-level object its nested Objects & List<>s were copied automatically. That is not the case anymore, in MongoDB's Realm each one has to be done manually.

    Built-in deep copying Objects is further important since:
    1) Using partition-based Realm leads to denormalizing your data, which means more copies (not horribly bad if a new object but if existing one then harder).
    2) Another reason why you need to denormalize your data is that Sync Permissions are determined at the partition-level, and not at the document level. It would have been nice to be able to use the ‘%%root’ as a JSON expression in Sync Permissions (and process are document level) to gain access to each document (aka: object) being processed - in order to allow / restrictions read or write permissions.

    Please have the SDKs allow to copy objects from one partition to another. Currently you have to manually do it, which isn't great but not horrible, until your object has nested Objects, List<>s or EmbeddedObjects (via referenced 'foreign_key' / _id) - that is when it gets nasty and cumbersome. In Legacy Realm when ever you copied a top-level object its nested Objects & List<>s were copied automatically. That is not the case anymore, in MongoDB's Realm each one has to be done manually.

    Built-in deep copying Objects is further important since:
    1) Using partition-based Realm leads to denormalizing your data,… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. New feature to know whether or not server sync is enabled on client app

    Currently, I see the Java SDK has no properties or functions to tell the client app whether or not server sync is enabled.
    Use case: if client app has DiscardUnsyncedData as client reset strategy, I don't want users to use offline Realm when server sync is disabled. There should be some features in the Java SDK to say whether or not sync is enabled.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Angular support

    I am extremely excited about Realm. To my current understanding the realm-web npm package does not fully support Angular framework.
    Is that so or am I wrong?
    If so is there an estimation as to when will Angular be supported please? thank you!!!

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. collection.watch support on React Native

    Although in the documentation as working, this doesn't work (https://github.com/realm/realm-js/issues/3494) I pretty much built everything on Realm expecting this to work as documented.
    It should be noted in the docs that this doesn't actually work. If there is a workaround available would be great to know about it, haven't been able to get it to work yet.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Query Realm using MongoDB syntax

    Now that Realm and MongoDB are so close, it would be nice to be able to use MongoDB-style queries on Realm as well. It seems to me that an object-based query language makes much more sense than a string-based one nowadays.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Realm Google Authentication Providers callback redirect

    Hello, I am having problems with authentication via Google Authentication Providers.

    The system prevents me from saving the backlink as:
    chrome-extension://feomclaleplfhikikgnedghpnhozzzhb/index.html

    Throws an error: redirect URI must contain scheme of http or https
    "chrome-extension://" is the standard URI scheme.

    Please add the ability to add a schema backlink for the chrome extension.

    I cannot use other Google Authentication Providers because, if you build the application in the ElectronJS + Chrome-Extention configuration, ElectronJS does not support any authentication protocols. The only way out is to log in using the back link.

    Regards, Alexander

    •  

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Support for MongoDB Transactions within SDKs

    Is it possible to support MongoDB Transactions within the SDKs?

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Realm (General)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close