im a bit confused about the correct way to name the columns in my imported data.
if i have two tables with one to one relation. and the schema is already created in backendless.
i know on tableB i will have this column: reference__tableA__bcklsFK__ONE_TO_ONE
but how can i control tableA column that identify the relation?
but my reference doesn’t know backendless objectid
so when i import tableA data. backendless will auto create objectid data for tableA
but my reference in tableB is referring to other column in tableA.
You need to include objectId into the CSV and reference that value in the relations. The value of objectId can be your own (must be unique). This is what we show in the documentation as well. That’s the only way Backendless will understand that the objects are related.
The file should contain all your geopoints. The first column is the ID of each geopoint - a unique string which identifies it in the system. For example:
Suppose your geopoint references an object from table Address and the name of the metadata property is address. In this case, in your Address.csv you need to declare the following column:
address__GeoPoint__bcklsFK__ONE_TO_MANY
The value for that column should be id of the corresponding geopoint.
I didn’t quite understand what you wrote. However, the best way to learn how to format the data is to enter the data using Backendless console, create all the relationships and then run export to see how Backendless itself creates those CSVs. Then if you structure your CSVs the same way and import, it will work.
i tried a lot of times with no luck there is no metadata in geo point.
here is the test files. tell me what is wrong. store1.csv (77 Bytes) location.csv (40 Bytes)