89 results found

1. Remove Realm API retrieval limit

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

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Import app with Realm UI

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

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. realm-ui

   When creating a free cluster to evaluate realm-ui and sync please warn that 4.4 or higher mongo is required.
   Now i found out when getting started that i have a cluster with 4.2.1 and cannot use the task tracker app sync.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Add Subscription Payments for charging Customers/Users in MongoDB Realm Cloud

   MongoDB Realm is perfect for SaaS products but the hard part is always implementing recurring billing for customers, we would need to write and implement a system like this ourself and maintain it which costs time and money or use third party services like Chargebee or Recurly. Firebase already has a nice extension market where you can install the Stripe extension and you are ready to go and charge your Customers monthly, I would like to see the same in MongoDB Realm with Stripe & PayPal & maybe more, best would be as an official product of the MongoDB product family like Charts or Realm are, just call it MongoDB Realm Subscription Payments or something :)

   MongoDB Realm is perfect for SaaS products but the hard part is always implementing recurring billing for customers, we would need to write and implement a system like this ourself and maintain it which costs time and money or use third party services like Chargebee or Recurly. Firebase already has a nice extension market where you can install the Stripe extension and you are ready to go and charge your Customers monthly, I would like to see the same in MongoDB Realm with Stripe & PayPal & maybe more, best would be as an official product of the MongoDB product… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Compare Strings and ObjectIds in JSON Expressions

   We have a use-case where we need to compare an ObjectId on a document to the ObjectId of the user's custom data doc. However, because the ID of the user's custom data object is returned as a string and not as an ObjectId, there is no way to make this comparison without creating a function just to compare the ObjectId and the string. The overhead of invoking a function just to call toString on the ObjectId is going to be a major problem, especially because we need to make this comparison 5 times for every single operation on our most heavily trafficked collection.

   This could be easily solved by what should be a rather simple feature to add, an operator that could be used to compare an ObjectId to a string within JSON expressions.

   I think the best justification for this addition is that there are several situations where you simply cannot get an ID in ObjectId form as it is only provided as a string, like the ID on user custom data docs.

   We have a use-case where we need to compare an ObjectId on a document to the ObjectId of the user's custom data doc. However, because the ID of the user's custom data object is returned as a string and not as an ObjectId, there is no way to make this comparison without creating a function just to compare the ObjectId and the string. The overhead of invoking a function just to call toString on the ObjectId is going to be a major problem, especially because we need to make this comparison 5 times for every single operation on our most… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. 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 that I wouldn't be charged. The realm wouldn't disappear and could be turned back on either the next month or if I chose to accept the charges for additional resources. This would allow me to gauge my usage in the first few months without the worry of being charged.

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  App Services General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close