Skip to content

Atlas App Services

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

248 results found

  1. Special variables and values

    For example, I have a field called UpdatedAt which is a datetime field, I'd like to have it set to the system datetime of the server. If I use trigger to update the value of this field, then I will not be able to read the value right after the mutation completed. So I want to do something like ' Field: SYSTEMDATETIME', then the server side of GQL will translate SYSTEMDATETIME to the correct value.

    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)
  2. Ability to query datalake / online archive

    The new online archive is awesome.

    What would be even better is if we could query the data it moves to S3 as part of our stitch/realm functions.

    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)
  3. Disable Realm

    It would be great to be able to disable a realm without deleting it. Currently, this is possible by unlinking the cluster or exporting the realm and deleting it. Both of which create more work when firing it back up.

    It would also be amazing to be able to tie that in with billing alerts. Say I would rather my app crash than pay more than a certain amount because of Realm usage.

    In essence, I'm asking for an "always free" Realm that just disables itself when the free tier has been hit so that I can be 100% certain…

    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. Availability of Args in Function Context

    Not sure if this is do-able already or not. Couldn't find documentation.

    I have a function that looks like

    exports = function(dbName, collectionName, pipeline){...

    I want to be able to access the arguments sent to the function in the Can Evaluate JSON expression.

    I assumed it might work like

    {
    "%%args.dbName": "eflex-test"
    }

    but that doesn't seem to work

    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)
  5. Access to %%args in Filters

    Allow the access to %%args in filters. This would make it possible to make the apply_when of filters more dynamic by accessing the incoming queries. As of now, filters are completely static due not having access to any incoming information.

    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)
  6. Broader Push Notification Support

    I've moved from Firebase because of the lack of support for React-Native and I've just discovered that I need to use Firebase to receive Push Notifications from my App. I'm aware of the complexity of adding this layer to SDKs, but you're already much ahead of Firebase in terms of SDK maintenance and support, being able to make a full app's stack would be wonderful for many, I think.

    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. RDBMS Connectors

    Make the previously available data connectors available for Realm’s data adapter to sync data from the Realm Object Server to a Microsoft SQL Server and vice versa.

    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. Human readable URLs in UI

    Currently, the app urls are extremely long and unreadable, for example: https://realm.mongodb.com/groups/5ab028594e6581148629dc65/apps/5b28f4615fdce07a74cd7f50/triggers/5bcf226fe707c05350750dcc
    This looks pretty ugly. It would be a lot more user friendly to:
    - eliminate the /groups/<groupID>/ portion of the URL entirely - the app ID already uniquely identifies the group anyway
    - use the clientAppID instead of the raw objectID for /apps/<appID>.
    For example, the above URL could instead be represented as
    https://realm.mongodb.com/apps/my-app-xyz/triggers/5bcf226fe707c05350750dcc
    with no loss of functionality or precision

    0 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)
1 2 9 10 11 13 Next →
  • Don't see your idea?

Feedback and Knowledge Base