248 results found

1. More descriptive errors

   We need more error codes for different situations. For example, using the wrong details while logging in returns 46 (Unknown), with a message indicating wrong credentials. In my app, 46 maps to a message like "An unknown error occurred. Please try again later.".

   It would be nice if wrong credentials had its own error type so I could send a more descriptive message.

   Please also consider this for any other error type that doesn't have a good reason for being Unknown.

   Thanks!

   9 votes

   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  ·  App Services 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

2. Logging Enhancements

   We need the following enhancements
   1. Need more than 80 characters
   2. Need ability to turn it on and off by level (Log4J)
   3. Need ability to turn to higher level of logging on a single call

   9 votes

   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  ·  Developer Experience  ·  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. Support $[<identifier] with ArrayFilters feature

   Permit to use this operator:

   https://www.mongodb.com/docs/manual/reference/operator/update/positional-filtered/#mongodb-update-up.---identifier--

   8 votes

   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  ·  Data API / HTTPS Endpoints  ·  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. Customize Reset Password Email Link

   Users should be able to customize the reset password email that is sent to their users. This should include changing what the "sender" url looks like (noreply-stitch+mongodb.com => resetPassword@yourapp.com). Developers should have access to change look of the body of the email. This includes what is typed in the body, the title of the body and as well the company logo. I will upload a picture of how it currently looks and from my message understand what we want to change.

   •  

   8 votes

   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  ·  App Services 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

5. More Intuitive GUI for Relationship Modeling

   I know "Add Relationship" button works very well. However, you can check some of Headless CMS out there and learn from how they are letting users to handle relationship modeling.

   I think the one from Strapi is the best. It's like attached image.
   You can search on google image by "Strapi relation" and find more images.

   •  

   8 votes

   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

   started  ·  0 comments  ·  App Services 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

6. Single schema of truth: JSON Schema / Realm Schema / GraphQL Schema / TypeScript Types

   I think the current recommended initial prototyping workflow for a Realm web SDK user is like this:

   1) Add first data in collection (manually, on Compass etc.)
   2) Generate JSON Schema (manually click a button on web UI)
   3) Set up relationship (manually, on web UI)
   4) Download GraphQL Schema (manually click a button on web UI)
   5) Get TypeScript types and React hooks (automatically generated by graphql-codegen CLI)
   6) If you use another Realm SDK somewhere else (ex. Node.js sdk for server side), write Realm Schema (manually)

   This is not very developer friendly, and requires back-and-forth work between CLI, browser, VSCode, and Compass etc. It is not a one-time operation; you need to repeat it whenever you change your model structures, which frequently happens when you prototype.

   What I think the ideal way is AWS Amplify's one. In Amplify, you just:
   1) Write (a part of) GraphQL schema on editor
   2) Run a CLI command to apply

   Although I noticed pro/cons, it feels like Realm is going with data-first approach. If we can use schema-first approach too, it will be more wonderful. It will be great to have a single source of schema.

   At this moment, it seems developers are required to manually check all the schema are aligned and the same, if I understand correctly.

   PS. I also checked if I can use mongoose ORM. It seems it also requires another schema of its own.

   I think the current recommended initial prototyping workflow for a Realm web SDK user is like this:

   1) Add first data in collection (manually, on Compass etc.)
   2) Generate JSON Schema (manually click a button on web UI)
   3) Set up relationship (manually, on web UI)
   4) Download GraphQL Schema (manually click a button on web UI)
   5) Get TypeScript types and React hooks (automatically generated by graphql-codegen CLI)
   6) If you use another Realm SDK somewhere else (ex. Node.js sdk for server side), write Realm Schema (manually)

   This is not very developer friendly, and requires back-and-forth work between CLI,… more

   8 votes

   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

   6 comments  ·  GraphQL API  ·  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. Disable Sync

   A flag to enable/disable cloud sync on Fully-synchronized realms.

   This would be convenient if you're offering sync as a premium feature.

   8 votes

   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  ·  Device Sync  ·  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. MongoDB Realm vs Realm

   Hi, I am an existing Realm/Realm Cloud user and am struggling to understand what the MongoDB Realm offering is and how it compares with the existing Realm/Realm Cloud solution.

   Is there any documentation that explains what the difference is between the two solutions and what if any migration is required.

   It's not clear whether the latest cocoa Realm database v5.1.0 is still compatible with Realm Cloud nor is it clear whether there is any plan to continue supporting the current Realm Cloud solution. A nice clear description would be much appreciated.

   Regards
   Duncan

   8 votes

   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  ·  Developer Experience  ·  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. function sandbox

   It would be great to have a function sandbox area, where you can write and called previously used functions (saved like notepad++ does) without having to create the function and commit it.

   This would be for trying thing out or performing quick tasks for which you don't want to go through all the hassle of formally creating a function.

   8 votes

   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  ·  Functions  ·  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. Allow manually disabled trigger to resume without resume token

    I am filing a feature request for the option to: Disable a trigger manually and be able to restart it without using a resume token (i.e. such that DB events that occurred while it was disabled will be ignored by the trigger, and it will simply start listening for new events upon restart).

    8 votes

    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

    planned  ·  2 comments  ·  Triggers  ·  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. Application Deployment in GCP

    Currently deployent is only available to AWS but Atlas allows deployment in GCP.
    
    We need to have deployment close to GCP for better performance consideration.

    7 votes

    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

    planned  ·  0 comments  ·  Developer Experience  ·  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. Atlas App Services regions in the UK

    UK Data Protection requirements often require data to reside within the UK, something that cannot be supported through Atlas App Services today.

    For all features (especially Charts, Realm and Triggers), being able to select the UK as a region would unlock additional customer use cases.

    Given I am a UK domiciled MongoDB Atlas user
    When I use MongoDB Charts
    Then all traffic should remain within the UK

    Given I am a UK domiciled MongoDB Atlas user
    When I use MongoDB Atlas Triggers
    Then I should have the option for my trigger to invoke from a UK data center

    Given I am a UK domiciled MongoDB Atlas user
    When I use MongoDB Realm
    Then I should have the option for my Realm app to be hosted in a UK data center

    Given I am geographically based in the UK
    When I use MongoDB Charts
    Then all traffic should remain within the UK

    UK Data Protection requirements often require data to reside within the UK, something that cannot be supported through Atlas App Services today.

    For all features (especially Charts, Realm and Triggers), being able to select the UK as a region would unlock additional customer use cases.

    Given I am a UK domiciled MongoDB Atlas user
    When I use MongoDB Charts
    Then all traffic should remain within the UK

    Given I am a UK domiciled MongoDB Atlas user
    When I use MongoDB Atlas Triggers
    Then I should have the option for my trigger to invoke from a UK data center

    Given I… more

    6 votes

    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  ·  App Services 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

13. Realm Trigger Event Projection should support exclusion

    Realm triggers with a projections must include "operationType": 1. This makes excluding fields impossible because, according to the documentation:

    if you exclude fields, you cannot also specify the inclusion of fields

    The only work around we have found is to list every single field in the database and this would require an update anytime we add another field to the model. This is quite cumbersome and should be easily resolved with a simple exclusion.

    6 votes

    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  ·  Triggers  ·  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. Client Side Field-level encryption for Realm Sync

    Support client-side field-level encryption in MongoDB Realm.

    https://docs.mongodb.com/manual/core/security-client-side-encryption/
    https://docs.mongodb.com/manual/core/security-automatic-client-side-encryption/

    Basically, it would be nice if we could mark fields as being "sensitive" in the schemas, and Realm Sync would make sure to encrypt the fields before they are sent from the client app to the MongoDB Atlas database.

    6 votes

    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  ·  Device Sync  ·  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
    AdminOtso (Admin, MongoDB) responded

    Here's an example on client side encryption with Realm Kotlin SDK on Android https://github.com/realm/realm-kotlin-samples/tree/main/AppServicesUsageSamples/apps/property-encryption

15. Array types in generated GraphQL schema should follow JSON schema of a collection or custom type

    Hello!

    Realm generates GraphQL schema that does not reflect the exact JSON schema of a collection or custom type when it comes to array fields. Generated GraphQL schema allow arrays to contain NULLs even if this is not stated in JSON schema.

    For example, please see collection schema in the attachment. (Not able to insert JSON here in a readable manner)

    For this schema, I expect Realm to generate following GraphQL type for my collection:
    
type MyCollection {
_id: ObjectId!
arrField: [String!]!
}

    Please note the exclamation sign inside the square brackets. This states that the array item can only be a string, no nulls or other types are allowed - exactly what is defined in JSON schema above.

    But instead, Realm generates following:
    
type MyCollection {
_id: ObjectId!
arrField: [String]!
}

    So, it makes array element nullable, which looks like a bug and results in typecheck issues in client apps that are using generated GraphQL schema.

    Related topic on forum: https://developer.mongodb.com/community/forums/t/graphql-schema-wrongly-allows-nullable-values-as-array-items/106005

    I think this behavior is confirmed to be a bug there. Would be very nice to have it fixed or at least have an explicit way to make array elements not nullable.

    Hello!

    Realm generates GraphQL schema that does not reflect the exact JSON schema of a collection or custom type when it comes to array fields. Generated GraphQL schema allow arrays to contain NULLs even if this is not stated in JSON schema.

    For example, please see collection schema in the attachment. (Not able to insert JSON here in a readable manner)

    For this schema, I expect Realm to generate following GraphQL type for my collection:
    
type MyCollection {
_id: ObjectId!
arrField: [String!]!
}

    Please note the exclamation sign inside the square brackets. This states that the array item can only… more

    •  

    6 votes

    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  ·  GraphQL API  ·  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. Support of multiple partition keys

    You could actually increase the awesomeness of MongoRealm, when you support multiple partition keys on one object.

    Example:
    We have a collection of customers in MongoDB, our App is showing the customer information to the users, but only for those users, that are "allowed" to see the customers. So the customer object has a partition key holding the userName it is assigned to:

    customer { _id: "12345", partition: "bob", name: "MongoDB Inc."}
    customer { _id: "12346", partition: "alice", name: "Microsoft"}

    now we want, that alice also sees the customer "MongoDB Inc." in the App.

    The solution could look something like that:

    customer { _id: "12345", partition: ["bob","alice"], name: "MongoDB Inc."}
    customer { _id: "12346", partition: "alice", name: "Microsoft"}

    So that object with id "12345" will be distributed in the realm for alice and also in the realm for bob. MongoRealm will take care of all the nifty synchronization stuff.

    You could actually increase the awesomeness of MongoRealm, when you support multiple partition keys on one object.

    Example:
    We have a collection of customers in MongoDB, our App is showing the customer information to the users, but only for those users, that are "allowed" to see the customers. So the customer object has a partition key holding the userName it is assigned to:

    customer { _id: "12345", partition: "bob", name: "MongoDB Inc."}
    customer { _id: "12346", partition: "alice", name: "Microsoft"}

    now we want, that alice also sees the customer "MongoDB Inc." in the App.

    The solution could look something like… more

    6 votes

    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  ·  Device Sync  ·  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. Deployment integration with gitlab

    Deployment connection to github.

    •  

    6 votes

    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  ·  Developer Experience  ·  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. Google Pubsub Client Support

    support Google Pubsub Client API's in functions

    6 votes

    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  ·  Function JS Package Support  ·  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

19. Allowed Request Origins should support URLs with wildcard characters

    The Allowed Request Origins list in the App Settings, at this time, doesn't support URLs with wildcard characters. As modern services like Vercel generate dynamically new URLs during development, the list needs to be updated every time with the current URL, while having an option available that would accept "https://*-myappname.vercel.app/" would simplify that step.

    5 votes

    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

    2 comments  ·  App Services 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

20. Trigger event queue metrics

    We recently ran into the problem that our trigger was suspended because the resume token was no longer present in the oplog.
    The problem was a combination of queued up trigger events and a short oplog window and the suggested solution was to increase the triggers performance by parallelizing it and by increasing the oplog size to get a bigger oplog window.

    Unfortunately, we're not able to verify the real success of these suggestions, because even though we can monitor the oplog window in the metrics, there are no metrics for the trigger queue itself. As a result, we can't see how close to our oplog window this trigger queue comes and therefore we're not able to predict a potential suspension in the future.

    Our suggestion is to include some metrics for the trigger queue. Examples could be the number of events in the queue or the age of the oldest event in it.

    We recently ran into the problem that our trigger was suspended because the resume token was no longer present in the oplog.
    The problem was a combination of queued up trigger events and a short oplog window and the suggested solution was to increase the triggers performance by parallelizing it and by increasing the oplog size to get a bigger oplog window.

    Unfortunately, we're not able to verify the real success of these suggestions, because even though we can monitor the oplog window in the metrics, there are no metrics for the trigger queue itself. As a result, we can't… more

    5 votes

    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  ·  Triggers  ·  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