[Feature] Firestore DB needs additional API support to ingest certain data types / formats

[somangshu]

Description

When the user tries to use unix time stamp moment(EventAddStartDatePicker.selectedDate).unix() in the firestore API, the DB treats is as a map instead of timestamp. Instead when the user tries to use the firestore wrapper to do so, the function works properly admin.firestore.Timestamp(moment(EventAddStartDatePicker.selectedDate).unix(), 0)

The user wants support for the Firestore fields such as references, geocoordinates, etc.

Important Details

• Version: [Cloud / Self-Hosted vx.x]
• OS: [e.g.MacOSX]
• Browser [e.g. chrome, safari]
• Environment [production, release, deploy preview]

[tazmaniax]

Yes, something like this in the query body might be useful at least for the Timestamp field building a document reference would also be needed. You could then probably get rid of the "Timestamp value path" because that could be done with admin.firestore.FieldValue.serverTimestamp()

{{
{
  "code": EventAddCodeInput.text,
  "title": EventAddTitleInput.text,
  "start": EventAddStartDatePicker.selectedDate ? new admin.firestore.Timestamp(moment(EventAddStartDatePicker.selectedDate).unix(), 0),
  "end": EventAddEndDatePicker.selectedDate ? new admin.firestore.Timestamp(moment(EventAddEndDatePicker.selectedDate).unix(), 0)
  "extPlatform": EventAddExtPlatformSelect.selectedOptionValue,
  "extReference": EventAddExtReferenceInput.text,
  "createdBy": appsmith.user.email,
  "created": admin.firestore.FieldValue.serverTimestamp()
}
}}

[tazmaniax]

Somewhat related is that Firebase is moving to a more modular API, v9. I wonder if you need to wrap this API to expose it within Appsmith then maybe the new v9 API might make that task easier.

[somangshu]

Thanks for the additional info here @tazmaniax

[tazmaniax]

This is similar to #3741

[tazmaniax]

Hi, is there a rough timeline when this might be resolved? thx!

[tazmaniax]

Now it's Hactoberfest, maybe I need to roll up my sleeves! 😄

[GreenFlux]

Another user is requesting support for Firebase timestamps:
https://discord.com/channels/725602949748752515/1221163808706400317/1221163808706400317

[Naveen-Goud]

hello @somangshu , I have worked on this task and here are my observations ,
"I observed that the app's data is directly stored in Firestore as a collection without considering data types. This results in collections being improperly displayed in Firestore, as the data is stored as JSON, converted into a hashmap with key-value pairs, and then saved. To address this issue, I created a method that takes the hashmap as input and returns the data with proper data types, allowing it to be saved as expected."
so for that firstl add this code snippet in MethodAddDocument.java

Now everything is working fine and here is the screenshot for the example input

output
.

This approach ensures that the data is stored with the appropriate types, improving the readability and integrity of the data in Firestore.

would you please share your thought on this??

thanks

[Naveen-Goud]

Hello @tazmaniax , I have raised the PR for this task, Could you please review it.