Hey,

is there any difference between uploading a fileReference (image in this case) to a data-collection or the user-collection?

Saving a fileRef and an id to the user just save this two variables inside the (in this case) "avatar" object in the user-Collection.

On my data-collection (same code) there are also values for the download-url, size, _kmd stuff etc.


I need that addional data inside the avatar of the user, too - so how can i achieve this?

 

Kinvey.Backbone.getActiveUser().save({
				'avatar' : {
					_type : 'KinveyFile',
					_id : file._id
				}
			}).then(function(response){
				console.debug("Image ::: assigned to User");

});

Doing like above

 

Best, Nico

 

Thanks, I'm looking forward to more infos from you.

Best,
Nico

*push*

Cause i don't want to create an ugly workaround for this.


Best, Nico

Hey,

thanks for your answer!


I'll try to be more clear:

My situation is, that i have profil-Images ("avatar") for both, users and groups, users can be member of.

The difference is, that kinvey seems to handle the User Collection a little bit different to a normal "data collection".


Saving the fileReference to the datacollection ("squads" in this case) , result in an object containing the downloadURL to the file and all other kinds of informations. (Which is great)

Saving the fileReference( same client code) to the user-Collection results in something like this:
{"_type":"KinveyFile","_id":"ace8c075-bf8b-4ef4-a2bc-613821d7d59f"}

As you can see, there is only the fileID and none of the addional informations, that are automaticly added, saving it to a normal datacollection.


So my workaround idea is, after the user saves the file as his/her profil image, i call the download url and stuff by myself, and update the object, too. So the main question is (i guess) why do you handle that collections differently in this case, cause to me it doesn't make sense. :P

best, Nico