Skip to content

Atlas App Services

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

262 results found

  1. Support relationships for fields inside arrays of embedded objects in GraphQL

    Currently, as explained in the App Services documentation, the "GraphQL API does not currently support relationships for fields inside arrays of embedded objects. You can use a custom resolver to manually look up and resolve embedded object array relationships."

    There is a contradiction with this other documentation that explains it's possible: https://www.mongodb.com/docs/atlas/app-services/schemas/relationships/#embedded-object-within-a-list

    But it's not possible.

    For example, with this schema:

    {
      "title": "Person",
      "properties": {
        "_id": { "bsonType": "objectId" },
        "pets": {
          "bsonType":"array",
          "items": {
            "title":"PersonPet",
            "bsonType": "object",
            "properties": {
              "favoriteToyBrand": { "bsonType": "objectId" }
            }
          }
        }
       // ...additional model properties
      }
    }
    

    and this relationship:

    {
      "pets.[].favoriteToyBrand":
    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  GraphQL API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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!

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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,…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  GraphQL API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Device Sync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  Triggers  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Allow to pass user on Realm's Database Triggers

    Currently I can create a Database Trigger, that when calling its Function I can restrict based on "%%user" - through "Can Evaluate". Though since the Function is called by a Trigger and therefore runs as a "system user" I cannot access the User object (or its details) within the Function - I (personally) mainly want the userID & email - though whole object would be better.

    Since a Function is called by a Trigger and therefore it runs as "System User" - Please allows us to pass an array of arguments for the Function. This could be a field after…

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Triggers  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Triggers  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Device Sync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  GraphQL API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Device Sync  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Google Pubsub Client Support

    support Google Pubsub Client API's in functions

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Triggers Integration with Azure Event Grid

    We have “Event bridge” integration with Atlas Triggers today. Adding Azure Event Grid support will be very helpful in building no-code solutions like real time sync for ODS/ ODL etc for Azure.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Triggers  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base