__skuid_record__.row causes JSON.stringify circular structure error on REST model PUT operation for

Attempting to use the “Automatic” option source fails, because for some reason skuid is interpreting the assignee field from bitbucket as a string rather than as an object:

Interestingly, a different model on the same page, with the same source (this one read only to create a list), shows the assignee field as an object:

That’s what I need for the model in the OP! How can I get skuid to re-interpret or fetch new metadata for my model so that it correctly understands that assignee is actually an object and not a string?

Ah, looks like the Composer Settings field on the Page object is what I needed!

Well, having the assignee field as an object instead of text is nice, but it’s not getting me anywhere.

Any guidance on setting up a reference field for a REST model like this?

Well, look like if I just set the assignee.username field to render as a picklist, with my Team Members model as a picklist options source, things seem to work out just fine.

It would still be nice to know how to actually set up a reference field on a REST model like this.

Matt~

Sounds like you were able to answer your own question eventually? Just want to confirm you’re all set. We will bring this idea up with our documentation team. 

Thanks!
Karen 

I’ve got it working now after a lot of trial and error. it would be great if skuid could document reference fields for rest models more thoroughly, and explain the circular JSON error I described.