I noticed with the growing size of my database responses, the number of “___objectref” fields in the json structure rises. These are always there instead of loaded relations. It seems this field replaces a related object which was already previously in the return string from the database.
In my mail you can find a response from my API fetched over the Backendless Console which gives this command:
-X “GET” “https://api.backendless.com/63087FF7-7E1D-973D-FF3B-D5F0740FA100/5C363F28-6536-9660-FFAF-2B85F9EDFB00/services/EightCloudService/acquisition/metadata?ID=-1&Offset=0&Shareddata=false&Deleted=false”
-H ‘Content-Type: application/json’ \
-H ‘Accept: application/json’ \
-H ‘user-token: 531BC87D-C621-7D37-FF64-D6DE596B9F00’
I hope you can fix this or give me a hint how I can avoid this, as this stops my logic and GUI from working properly, as there are obviously data missing in the json tree where the program expects the omitted objects.
Thanks and Best regards