118 results found

1. Allow cross-project restoring of Firestore databases

   When working with Firestore databases, you may want to restore an entire database for testing in your stage project.

   However, currently, you can only restore in the same project

   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  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

2. rules map

   In Firebase Firestore rules, we currently have various controls and functions, which are very handy. However, array management is not optimal. I propose introducing a map function for arrays in Firebase Firestore rules. This function would allow us to map arrays of objects, significantly simplifying the creation and management of rules.

   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  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

3. Allow to assign tags to Firestore databases

   With multi-db support in Firestore now launched, this enabled many possibilities but also requires more granular inventory management of the databases created.

   --

   For compliance reasons and for better management of your cloud assets, it's important to assign metadata to your cloud resources.
   Especially for storage services, this is important, as it allows you to track which resources contain PII, who owns them, etc.

   --

   Attaching this kind of data is typically done using tags in Google Cloud.
   If it would be possible to attach tags to individual Firestore databases, this would solve the management of databases and allow easier compliance management.

   --

   For example, it could allow your compliance automation software (like Vanta or Drata) to extract that information directly from Google Cloud while allowing your engineers to define those labels right where they provision the database.

   With multi-db support in Firestore now launched, this enabled many possibilities but also requires more granular inventory management of the databases created.

   --

   For compliance reasons and for better management of your cloud assets, it's important to assign metadata to your cloud resources.
   Especially for storage services, this is important, as it allows you to track which resources contain PII, who owns them, etc.

   --

   Attaching this kind of data is typically done using tags in Google Cloud.
   If it would be possible to attach tags to individual Firestore databases, this would solve the management of databases and allow easier… 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  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

4. Allow to attach IAM permissions to databases

   With multi-db support in Firestore now launched, this enabled a ton of new features, though the way permissions are granted is not ideal.

   --

   Instead of being able to attach permissions to individual databases, you have to use conditional IAM permissions on a project level.

   --

   This leads to problems when you want to grant IAM permissions to employees with access to only a subset of databases.
   Granting a subset of databases to access will prevent them from using the Firebase / Google Cloud console, as they will not have permission to view all databases.

   --

   Also conditional IAM permissions are more complex to setup and maintain.

   --

   A better solution would be able to attach IAM permissions directly to the databases, like it's possible for storage buckets, Secret Manager secrets, BigQuery datasets and tables, etc.

   --

   If someone doesn't have permissions to view a Firestore database at all, it should be excluded from the list of databases in the consoles.
   If someone does have the permission to view a Firestore database, but does not have permission to view the data, it should be shown in the list of databases but then not load the data when going to the data tab of the database.

   With multi-db support in Firestore now launched, this enabled a ton of new features, though the way permissions are granted is not ideal.

   --

   Instead of being able to attach permissions to individual databases, you have to use conditional IAM permissions on a project level.

   --

   This leads to problems when you want to grant IAM permissions to employees with access to only a subset of databases.
   Granting a subset of databases to access will prevent them from using the Firebase / Google Cloud console, as they will not have permission to view all databases.

   --

   Also conditional IAM permissions… 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  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

5. Allow use of the filter value on whereArrayContains within a firestore rule

   I believe that by simply allowing access to the whereArrayContains filter value, it should be possible to solve for a use-case which can generally only be resolved using an SQL/relational database or cloud functions.

   Take the following query;

         getDocs(
           query(
             collection(db, "profiles"),
             where("groupProfileLinkIdReference", "array-contains", "groupProfileLinkId1"),
             limit(1),
           ),
         )
   

   If we can access the value which in this case is "groupProfileLinkId1", it becomes possible to do the following;

   match /profiles/{profileId} {
         allow list: if validateListProfileDbEntry();
   }
   
   function validateListProfileDbEntry(){
     let groupProfileLinkId = resource.data.groupProfileLinkIdReference[0];
     let groupProfileLink = get(/databases/$(database)/documents/groupProfileLink/$(groupProfileLinkId)).data;
   
   
     return groupProfileLink.isApproved == true;
   }
   
   

   The way the data is modelled is that every time a new groupProfileLink is created for a profile the groupProfileLinkId is added to the profile's groupProfileLinkIdReference array field.

   Db summary;

   profiles
     - profileId1
       - id: "profileId1"
       - title: "someProfile"
       - groupProfileLinkIdReference: ["groupProfileLinkId1", "groupProfileLinkId2"]
       ...
   
   groupProfileLinks
     - groupProfileLinkId1
       - id: "groupProfileLinkId1"
       - groupId: "groupId1"
       - profileId: "profileId1"
   
   

   hopefully this makes sense - it really seems like it would unlock many new possibilities

   I believe that by simply allowing access to the whereArrayContains filter value, it should be possible to solve for a use-case which can generally only be resolved using an SQL/relational database or cloud functions.

   Take the following query;

         getDocs(
           query(
             collection(db, "profiles"),
             where("groupProfileLinkIdReference", "array-contains", "groupProfileLinkId1"),
             limit(1),
           ),
         )
   

   If we can access the value which in this case is "groupProfileLinkId1", it becomes possible to do the following;

   match /profiles/{profileId} {
         allow list: if validateListProfileDbEntry();
   }
   
   function validateListProfileDbEntry(){
     let groupProfileLinkId = resource.data.groupProfileLinkIdReference[0];
     let groupProfileLink = get(/databases/$(database)/documents/groupProfileLink/$(groupProfileLinkId)).data;
   
   
     return groupProfileLink.isApproved == true;
   }
   
   

   The way the data is modelled is that every time… 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

   2 comments  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

6. Orderby('any_potential_null_field', excludeNull: false) should exist

   OrderBy should be able to return collection item when target property is null.

   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  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

7. structure and organization of Firestore collections: documentation

   Normally documentation about collections is done in a 3rd party tool like notion, jira, google docs (or notepad for the brave ones).

   After a while this easily becomes inconsistent due to ongoing changes throughout the project development. The same way as we document code directly in the code file, it'd be great to document collections directly in the firestore console.

   For this, something simple like a text input would suffice (ideally with some minimal markdown, but not mandatory). If developers need to add more detailed info or explanations (and make use of charts, designs, videos, whatever) they could simply add a link and direct to their favourite documentation tool.

   This documentation would be useful to add information about
   - collection structure
   - document versioning (very important in NO-SQL when changes in structure happen between app versions)
   - triggers and updates with cloud functions (eg first document is written, then triggers a cloud function that does X, and document gets updated with information Y

   Normally documentation about collections is done in a 3rd party tool like notion, jira, google docs (or notepad for the brave ones).

   After a while this easily becomes inconsistent due to ongoing changes throughout the project development. The same way as we document code directly in the code file, it'd be great to document collections directly in the firestore console.

   For this, something simple like a text input would suffice (ideally with some minimal markdown, but not mandatory). If developers need to add more detailed info or explanations (and make use of charts, designs, videos, whatever) they could simply add… 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  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

8. Support offline capabilities for mobile using React Native

   I can see offline capabilities for mobile using Kotlin, Java, Swift and Objective-C. I am requesting offline support for React Native application.

   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  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

9. Raise the Firestore Rules Expression Limit

   Raise the maximum expression limit for firestore rules to make more complex doc schema validation possible.

   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  ·  Firestore  ·  Edit…  ·  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

   Submit Rating

10. Allow developers to use the local Firestore database for free

    It'd be really nice if you could allow users to create local drafts, of small documents, for instance, and save them locally for free with Firestore.

    This way you wouldn't have to coordinate Firestore and its rules with some other database and client code nor would you have to choose the simpler option of getting charged for writes and reads on remote database documents that really only one user is supposed to write and read.

    Please note that while you could use the realtime database to save drafts, 1 it's not always easy to figure out whether that'd actually be cheaper, 2 it'd still be cheaper, even with the realtime database, to save drafts only locally for free and then only getting charged for the backup on the remote database.

    It'd be really nice if you could allow users to create local drafts, of small documents, for instance, and save them locally for free with Firestore.

    This way you wouldn't have to coordinate Firestore and its rules with some other database and client code nor would you have to choose the simpler option of getting charged for writes and reads on remote database documents that really only one user is supposed to write and read.

    Please note that while you could use the realtime database to save drafts, 1 it's not always easy to figure out whether that'd actually be… 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  ·  Firestore  ·  Edit…  ·  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

    Submit Rating

11. Expose subcollections as json fields

    Currently, subcollections are treated separately from fields in the UI. This seems like an arbitrary distinction - a subcollection is simply a json object under a document. You could do the same thing with a string field.

    The API could support retrieving subcollections as string fields in json format for a document. This would prevent the need to iterate over every document in a collection, then get a list of the subcollections, then retrieve the documents from those subcollections, etc. If worried about time required, since Firestore supports 100 nesting levels, perhaps the API call could include the nesting level to output and truncate the output accordingly.

    Currently, subcollections are treated separately from fields in the UI. This seems like an arbitrary distinction - a subcollection is simply a json object under a document. You could do the same thing with a string field.

    The API could support retrieving subcollections as string fields in json format for a document. This would prevent the need to iterate over every document in a collection, then get a list of the subcollections, then retrieve the documents from those subcollections, etc. If worried about time required, since Firestore supports 100 nesting levels, perhaps the API call could include the nesting level… 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  ·  Firestore  ·  Edit…  ·  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

    Submit Rating

12. Allow security rules to validate custom bearer tokens

    Currently, Firestore and Cloud Storage security rules req.auth property will only validate and accept Google-signed ID tokens from Firebase Auth/Identity Platform.

    This means that "user authentication rules" CANNOT be used if we rely on our own (or 3rd-party) authentication/token server.

    Proposal:
    Allow security rules to configure the token verification rules so that they can verify the token claims of a configured token authority. For example, tokens signed by a service account private key, or 3rd party auth server (aside from Firebase Auth/Identity Platform).

    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  ·  Firestore  ·  Edit…  ·  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

    Submit Rating

13. firestore 'in' 2d array order optional

    For some reason an 'in' wury with a 2d array also runs with a sort function. which is not provided or supported by other features such as ArrayUnion and ArrayRemove.

    the order should be an optional parameter because using a system where we must find all other documents that have the exact same features but maybe in a different order, is not possible. there is no native sort option when using ArrayUnion, and we've been taught through firestore arrays in general, that orders of items fundamentally shouldn't be considered to exist due to idempotency.

    TLDR:
    ArrayUnion does not support 'in 2d array' query logic
    we can't find where [["dog"], ["cat"]] === [["cat"], ["dog"]]
in ["dog","cat"] also returns ["cat","dog","fish"]

    For some reason an 'in' wury with a 2d array also runs with a sort function. which is not provided or supported by other features such as ArrayUnion and ArrayRemove.

    the order should be an optional parameter because using a system where we must find all other documents that have the exact same features but maybe in a different order, is not possible. there is no native sort option when using ArrayUnion, and we've been taught through firestore arrays in general, that orders of items fundamentally shouldn't be considered to exist due to idempotency.

    TLDR:
    ArrayUnion does not support 'in… 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

    1 comment  ·  Firestore  ·  Edit…  ·  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

    Submit Rating

14. Query language (like SQL) but for firestore to enable developers to share queries across the whole stack

    let's say that you have a Kotlin android app, Swift iOS app, a Dart Flutter app and cloud functions written in typescript.
    there should be a way to re-use shared queries across the whole stack.
    having a query language like SQL and pass those redundant queries across all apps that would be really efficient and could save developers a lot of time and it could produce less bugs.

    I'm not suggesting SQL, I'm suggesting to have a query language that's all.

    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  ·  Firestore  ·  Edit…  ·  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

    Submit Rating

15. Allow use of document value as query paramter

    Especially a parent value of a subcollection. For example, to be able to read data about a User while querying a subcollection called "Responses".

    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  ·  Firestore  ·  Edit…  ·  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

    Submit Rating

16. signInWithCustomToken using Python

    Hello,
    is it possible to use signInWithCustomToken to authenticate in Python and retrieve documents from a collection?
    Does it work in Python only with cred = credentials.Certificate('serviceAccountKey.json')?

    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  ·  Firestore  ·  Edit…  ·  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

    Submit Rating

17. A way to get collections in a document using the Unity SDK

    There's currently no way to get the collections existing in a document using the Unity SDK. ListCollectionsAsync exists in the .Net SDK.

    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  ·  Firestore  ·  Edit…  ·  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

    Submit Rating

18. Drop Down Menu for Automatic Aggregations

    There would be a Drop Down Menu somewhere in Firebase Console that allowed you to create automatic aggregations...

    For example:

    OnCreate Collection (Posts) -> From Collection (Users) Where Field (UserID) equals DocumentID (Users / UserID) -> Add Fields (displayName, phoneNumber, role)

    So new post would have userID object from user document on 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  ·  Firestore  ·  Edit…  ·  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

    Submit Rating