Skip to content

Atlas App Services

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

240 results found

  1. Configure Change Streams to publish via Web Sockets

    It would be great of configuring a change stream (with certain filter and projection etc) to publish messages via a standard web socket as part of realm BaaS

    put simply auto implementing backend server as detailed in

    https://www.mongodb.com/developer/how-to/subscribing-changes-browser-websockets/

    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)
  2. Create databases and collections via Atlas API

    I don't know if this would fall under Admin API or Data API but currently there's a gap where it's not possible to create databases or collections in Atlas via REST API. This is important for a customer I'm working with who wants to automate creation of databases from scratch.

    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)
  3. 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)
  4. FTP Access to Realm Hosting

    Uploading web apps into the hosting directory can be time consuming using only the ATLAS UI - specifically because the UI/UX does not support uploading entire folders. This means you have to re-create the folder structure, and upload specific files into specific folders rather than just uploading a single folder with all folders/subfolders.

    This problem could be easily solved by providing FTP access to the "hosting" section.

    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)
  5. Realm sessions

    Could you please add a "remember me" or option for longer sessions on the Realm / Atlas Web UI?
    Besides the annoying factor of daily/24h re-sign-in, a couple of times I lost function changes when working in a tab that was left open overnight and a save would fail due to a stale session.

    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  ·  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)
  6. Atlas Realm deployments to Canadian Datacenter

    We would like a deployment of Realm in a canadian datacenter either in AWS or Google Cloud.

    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. Additional Filters to App Users Page

    Add additional filtering capabilities to the "App Users" page. Currently you can only by "id". Im not sure if its due to our app setup but the "id" seems like a totally random generated id that is not associated to any data in our DB. It would be nice to filter based on name, createdTime, last login time, etc instead of just id

    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)
  8. Ensure Realm Documentation Matches Implementation

    "Int" is listed as a supported type for partition keys but it's not implemented. You should remove "Int" from the supported types since it's not supported.

    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)
  9. Support for dynamic Open Graph Protocol meta tags

    Ability to whitelist certain IP addresses for social media crawlers and send them to a function that does server-side rendering of the index.html page to create open graph protocol (https://ogp.me/) meta tags for a dynamic link preview depending on what the link is. This specifically applies for single-page webapps.

    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. Link Two Email Credentials

    Should be able to link two or (preferably) more different email address credentials to 1 realm user.

    Most obvious use case for this would be an app that has both a business domain, and a personal domain. The user can log in to their realm account with either their personal email addresses or their business email addresses.

    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)
  11. Disable/Enable all triggers at once

    It would be very useful to be able to disable/enable all triggers of realm application at once. It useful for instance when you restore data from backup or make some big changes, and it is not needed to run triggers on every change

    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. 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)
  13. changeEvent cluster name

    I want to be able to programmatically access the clusterName from change event or global variable for example:

    changeEvent.ns.cluster = <CLUSTER/SERVICE name>
    global.CLUSTER_NAME

    I need this when I want to perform an update on same collection/document after the trigger, but i don't want to hardcode the clusterName - because i have multiple environments - each has its own cluster (dev/sandbox/prod etc...)

    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)
  14. One-time scheduled triggers

    At the moment, MongoDb offers the ability to schedule triggers periodically using Cron Jobs. It would be really handy if a user could schedule a trigger to run only once and execute a function as my use-case requires.

    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

    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)
  15. Containerized Functions + Logging + Dependencies Improvements

    I believe most of the below asks would be resolved if you allowed containerized functions to be uploaded and we can have the correct execution environment.
    Allow larger function sizes
    Allow more larger dependency sizes
    Allow 256kb size per log entry
    Allow Unlimited log entries per function execution
    Output formatted logs, don't want to scroll right forever
    Add refresh button for logs
    Log arguments for triggered function automatically
    Don't truncate logs
    Allow logs to be streamed so that you don't need to refresh logs
    Increase execution time to 15-30 minutes
    Allow dependencies to be imported outside of function definition
    Allow…

    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)
  16. GitHub Deploy - pulling deletes standard files, like LICENSE, README.md, etc.

    If I make a change in the UI, deploy, then do a git pull on my local machine, the pull deletes my License, README.md, and .gitignore files. These are standard files and should not be changed on pull. It's like it's overwriting everything from scratch instead of just doing a diff. My repo is public and I need to include this basic info.

    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)
  17. More Mongo DB actions parity with the Node driver

    The actions available via https://docs.mongodb.com/realm/mongodb/actions/ do not match the API exposed by the Node driver.

    For example, the https://mongodb.github.io/node-mongodb-native/4.0/classes/collection.html#createindex function would be extremely useful for our use case, I can't see any method for programmatically creating indexes via Realm.

    For example, the https://mongodb.github.io/node-mongodb-native/4.0/classes/collection.html#bulkwrite function returns a completely different type from https://docs.mongodb.com/realm/mongodb/actions/collection.bulkWrite/, making unit testing our realm functions locally extremely difficult.

    I'm unsure what reasons there are for this disparity (especially when I can use the mongo node driver to connect locally to an Atlas cluster, but I can't use any of these methods in our deployed application in Realm).

    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)
  18. Realm update/replace logs

    I think an enhancement to the realm logs that explains the deltas (what has changed) on a given document for updates/replace would be extremely useful.

    At the moment we receive an ID and the type of change that has happened which is fine for an insert/delete.

    But to understand what has changed on the document for an update/replace would help a lot in diagnosing any issues we have seen with realm in the past.

    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)
  19. External Dependencies Should Be Per Function

    10mb compressed size constraint is very limited. Plus, dependencies are not siloed per function. Either uncap the dependencies constraint or allow dependencies to be uploaded per function, still with a higher compressed size constraint (preferably at least 100mb to support large dependencies such as for image processing).

    I think the thought was "functions are meant to be short running operations" but I think that is a huge assumption. Why not offer options for powerful compute that respond to database change events. Sure you may need to just update something else in the db, and that may be sufficient for some…

    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)
  20. Migrate Firebase Cloud Message from legacy HTTP to HTTP v1

    I am very happy with Push Notifications using FCM but currently, FCM has been update to HTTP v1 and I saw that MongoDB Push Notification still using the HTTP. With HTTP, I can't send an image in the notification payload (https://firebase.google.com/docs/cloud-messaging/android/send-image), also the data payload is different when I send message directly from FCM.

    I hope that MongoDB have plan to migrate Firebase Cloud Message from legacy HTTP to HTTP v1 (https://firebase.google.com/docs/cloud-messaging/migrate-v1)

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

Feedback and Knowledge Base