Skip to content

Atlas App Services

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

257 results found

  1. Support for updating nested fields in GraphQL mutations

    I want to do the equivalent of {$set: {"details.pm_stage": "...."}}

    export const UPDATEPROJECTDETAILS = gql
    mutation UpdateProjectDetails($query: PsprojectQueryInput!, $pmStage: String!) {
    updateOnePsproject(query: $query, set: {details: {pm_stage: $pmStage}}) {
    _id
    }
    }
    ;

    right now the whole "details" subdocument gets overridden

    4 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. ObjectId

    We need a way for ids to not have to be unwrapped from $oid before they are assigned as an ObjectId.

    Incoming data:

    {"_id":{"$oid":"..."}}

    Realm class:

    class Item: Object {
    @objc dynamic var _id = ObjectId.generate()
    }

    That's all that should be needed.

    So the default ObjectId class needs:

    enum CodingKeys: String, CodingKey {
    case oid = "$oid"
    }

    then in init(from decoder:Decoder)

    let container = try decoder.container(keyedBy: CodingKeys.self)
    try super.init(string: try container.decode(String.self, forKey: .oid))

    Do that when the .singleValueContainer() call fails.
    That way both use cases are satisfied.

    2 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. Copy functions from one cluster to another

    It would be great if you could copy a Realm Service or Function from one cluster to another. I find myself having to open two tabs and coping the function code then checking all settings are the same etc.
    We would normally dev on a "test" cluster then copy Service functions over to "prod" cluster. Or am I missing something?

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. more aws eventbridge options

    • Push multiple triggers to 1 Eventbridge eventbus
    • Use the eventbridge SDK from the AWS service (now its not available and i have to use a custom aws sdk import, increasing the trigger time x 10 vs the normal eventbridge connector).
    1 vote

    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  ·  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)
  5. Ability to Reuse Types in Custom Resolver Schemas

    We are in the process of migrating from a hand-implemented Apollo server to Mongo Realm, but are finding the inability to reuse types on custom resolvers to be a serious impediment.

    For example, we have a number of custom resolvers that use the same type to define a temporal interval, but we cannot reuse that type in the arguments for our custom resolvers as Stitch will throw an error upon encountering those duplicated types. Additionally, many of these custom resolvers return the exact same type, but if we try to reuse that same type definition Stitch will throw errors about…

    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  ·  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)
    planned  ·  Drew responded

    Hi Folks – This improvement is already planned and should be completed shortly.

  6. Allow us to regenerate realm appID

    Please allow us to generate new appIDs in case it is compromised.

    1 vote

    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)
  7. Allow upload of large files through Realm Functions

    Right now we have a 30s input timeout on Realm Functions. We can't upload large files.

    Users in my case uploads large images of 20Mbs, and videos ~50Mb.

    Would be great to see this change, right now we are unable to use Realm for that.

    Also, AWS S3 service has a 4MB limitation as noted here, but not sure, I was able to upload a 7.8MB file https://docs.mongodb.com/realm/services/aws

    1 vote

    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)
  8. Add 'Previously Used' column to table of functions

    Add a column indicating when each function was previously used in the functions screen.

    It would also be helpful to have some basic stats about each functions usage, like total usage count, used in last 30 days, and total usage as a % of all function calls.

    This would help you to find which functions are used most to make them as efficient as possible, and to remove ones that aren't used much.

    2 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)
  9. Ways to pause a Realm App

    It would be awesome, if there was a way pause a Realm App via functions.

    Currently we are pausing our cluster every night using a trigger. However that causes all our Realm apps' sync and triggers to crash, so I have to manually restart each of them every morning.

    It would be awesome if I could pause/unpause a Realm App from a function. Something like this, maybe:

    context.realm.app([app-id]).pause()
    context.realm.app([app-id]).unpause()

    1 vote

    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)
  10. Count Query with the existing QueryInput Filter

    I think this would be easy to implement, maybe its just to add a count to the pipeline.

    The idea is to have a Count query for each generated type from collection in schema.

    The output would be a Int.
    The input the QueryInput used already for findManys queries

    2 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)
  11. Logout trigger

    There's a trigger for login, but there isn't one for logout (as far as I can tell). I would like a trigger on logout as well to perform cleanup of any of the side effects from the login trigger.

    This request is really a result of a separate request that is more important (https://feedback.mongodb.com/forums/923521-realm/suggestions/42102031-decode-user-token) but if there was a trigger for both login and logout it would tie me over until then.

    1 vote

    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  ·  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. Decode user token

    Using Realm as an authentication service and a separate backend that then allows the user to connect to separate external APIs, I need to be able to verify that the user is an authenticated user and that their data (only email in this case) match those of the third party external API.

    The request to the third party API runs via admin API channels so it's critical to ensure the user is only able to manipulate their own data (orders, subscriptions etc).

    As far as I've been told there is no way to verify a user that logged into my…

    1 vote

    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)
  13. Remove Realm API retrieval limit

    Remove the 50 item limit on calls to the Realm API.

    1 vote

    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. Schema Definition/Validation: Descriptive Errors

    It would be nice to have a more descriptive error similar to the way Joi works when an insert fails due to schema definition. An error that points to the offending section of the schema.

    It's hard to debug with the current "insert not permitted" error.

    Thanks

    1 vote

    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. Import app with Realm UI

    You can export the realm app using the Realm UI, but you cannot import it.

    1 vote

    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. Email/Password Auth password requirement options

    Email/Password Auth currently only validates passwords to be from 6 to 20 character long.
    We need more requirement options, such as:

    Minimum length, which must be at least 6 characters but fewer than 99 characters. User chooses the min and max option.
    Require numbers
    Require a special character from this set:
    ^ $ * . [ ] { } ( ) ? " ! @ # % & / \ , > < ' : ; | _ ~ `
    The plus "+" and minus "-" sign do not meet special character requirements.
    Require uppercase letters
    Require lowercase letters

    2 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)
  17. Provide support for Paypal Node SDK

    I just would like to have added support for the PayPal-node-SDK module. Currently when you try to use it as a dependency it results in an error.

    The repo is located here:

    https://github.com/paypal/PayPal-node-SDK

    1 vote

    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)
  18. Ordering fields in Atlas

    The field's order doesn't respect the schema.
    Ordering fields when we use mutation with GraphQL.

    1 vote

    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)
  19. Add the ability to use a value to reference a database in a trigger

    It would be great if we could use values for the database reference in a trigger, instead of having to select a database from a drop-down.

    An actual use case:

    To be able to use Realm for our various staging areas, we have created multiple Realm apps. One for production, one for UAT, one for test, etc. Each of them pointing to the databases for their respective staging environment.

    We are using Github deployments, and we use a separate branch for each of the staging environments. So when something gets committed to the "deploy-test" branch, it gets to be deployed…

    3 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  ·  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)
  20. Allow modifying Sync permissions without having to terminate it. Maybe pause instead ?

    Currently only way to modify/add permissions to Sync is at the beginning or terminating it. It would great if we could modify/add them with Sync Running or at least only pause it to avoid downtime and deleting cache from sync.

    3 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)
  • Don't see your idea?

Feedback and Knowledge Base