Realm

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Extend update and delete change event with document pre-image

    Hey,
    it would be really helpful to extend update and delete change events with pre-image of the document.

    Update event:
    For update events we can add a lookup to get the fullDocument but we do not have any information how the document looked before the update was applied.

    Delete events:
    In case of delete change events the only information regarding the document is the "_id" of the deleted document. It would be great to have the fullDocument in the change event to use this for further actions.

    Is an extension like this possible or even in development?

    Best regards
    Peter

    5 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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).

    5 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  3. Configure Realm notifications

    Currently only all project owners of the Atlas project in where your Realm app situates will receive notification of suspended trigger. This currently cannot be customized. We want to have the possibility to configure the notifications to include additional emails, not only for project owners.

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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…

    2 votes
    Sign in Sign in with your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Realm Triggers  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base