Not backing up documents with no fields but with subcollections

[martinkronstad]

I have a database with some documents that have subcollections, but no fields.

like this:

/orgdata/ORGID/firstSubCollection
/orgdata/ORGID/secondSubCollection
/orgdata/ORGID/thirdSubCollection

The document ORGID has no fields, since it is really just a sepeator for different userspaces.

[manwithsteelnerves]

Documents with no fields and collections alone are not valid on firestore. Those shouldn't be accessible too.
The only option is to add at least one dummy field to make it accessible correctly.

[atlanteh]

@manwithsteelnerves I think that's not true. Please see here:
https://firebase.google.com/docs/firestore/data-model#subcollections

Warning: Deleting a document does not delete its subcollections!
When you delete a document that has associated subcollections, the subcollections are not deleted. They are still accessible by reference. For example, there may be a document referenced by db.collection('coll').doc('doc').collection('subcoll').doc('subdoc') even though the document referenced by db.collection('coll').doc('doc') no longer exists. If you want to delete documents in subcollections when deleting a document, you must do so manually, as shown in Delete Collections.