You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a flamelink project from 2 years ago (Project A). We are now creating a new flamelink project (Project B). The schemas between Project A and Project B were created in the same way through the flamelink UI. The issue is that the Media Field (images) in Project B are stored as a reference in Firestore Database, where as the Media Field (images) in Project B are stored as a string.
Did something change in Firebase or Flamelink that makes this happen? Is there a way to control the value stored in the field?
Thanks!!
The text was updated successfully, but these errors were encountered:
What's Up?
We have a flamelink project from 2 years ago (Project A). We are now creating a new flamelink project (Project B). The schemas between Project A and Project B were created in the same way through the flamelink UI. The issue is that the
Media Field
(images) in Project B are stored as areference
inFirestore Database
, where as theMedia Field
(images) in Project B are stored as astring
.Did something change in Firebase or Flamelink that makes this happen? Is there a way to control the value stored in the field?
Thanks!!
The text was updated successfully, but these errors were encountered: