The trick is that, in addition to populating the lookup field’s foreign key reference (e.g. “My_Related_Object__c”, “AccountId”) you need to populate the lookup field’s related object data itself (e.g. “My_Related_Object__r”, “Account”).

In our example here, we have 2 Models: one, on Account, contains a single Account record that we query for. We want to use this to prepopulate the “AccountId” field on a new Contact record stored in our other Model, called NewContact. We want to have the “AccountId” field prepopulated with the Account’s Id, but, as Peter describes, we have a Display Template set on the field so that we’ll see the Account’s Name AND its Billing Country:








Here is some Inline JavaScript that will accomplish this:

(function(skuid){&nbsp; &nbsp; <br>&nbsp; &nbsp;var $ = skuid.$;<br>&nbsp; &nbsp; $(function(){<br>&nbsp; &nbsp; &nbsp; &nbsp; var MyAccount = skuid.$M('MyAccount');<br>&nbsp; &nbsp; &nbsp; &nbsp; var MyAccountRow = MyAccount.data 0];<br>&nbsp; &nbsp; &nbsp; &nbsp; var NewContact = skuid.$M('NewContact');<br>&nbsp; &nbsp; &nbsp; &nbsp; var NewContactRow = NewContact.dataa0];<br>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br>&nbsp; &nbsp; &nbsp; &nbsp; NewContact.updateRow(NewContactRow,{<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AccountId: MyAccountRow.Id,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Account: MyAccountRow<br>&nbsp; &nbsp; &nbsp; &nbsp; });<br>&nbsp; &nbsp; &nbsp; &nbsp; // We need to go manually tell our Field Editor<br>&nbsp; &nbsp; &nbsp; &nbsp; // to re-render its "AccountId" field.<br>&nbsp; &nbsp; &nbsp; &nbsp; // Since a Field Editor registers itself as a List<br>&nbsp; &nbsp; &nbsp; &nbsp; // on our NewContact Model, we can do this&nbsp;<br>&nbsp; &nbsp; &nbsp; &nbsp; $.each(NewContact.registeredLists,function(){<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $.each(this.renderedItems,function(){<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;$.each(this.fields,function(){<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; if(this.id==='AccountId') this.render();<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;});<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; });<br>&nbsp; &nbsp; &nbsp; &nbsp; });<br>&nbsp; &nbsp; });<br>})(skuid);

Thanks Zach. In my script, I’m already populating the field “enrollment__r” with the target record name, and “enrollment__c” with it’s ID. Is that how it should work for a custom relationship field?

The key thing is that you want to populate “Enrollment__r” with the Enrollment record, not just its name, that way Skuid when parsing your custom Display Template will be able to examine the Enrollment record to find all of the fields that you request in your Display Template, not just the Name field.

So if we have:

var EnrollmentModel = skuid.$M(‘Enrollment’);
var EnrollmentRow = EnrollmentModel.datad0];
var NewModel = skuid.$M(‘NewModel’);
var NewRow = NewModel.datae0];
        
Then doing:

NewModel.updateRow(NewRow,{
     Enrollment__c: EnrollmentRow.Id,
     Enrollment__r: EnrollmentRow
});

is NOT the same as doing this:

NewModel.updateRow(NewRow,{
     Enrollment__c: EnrollmentRow.Id,
     Enrollment__r: EnrollmentRow.Name
});

It’s a subtle difference, but an important one.

Ah yes, sorry, that is what I meant - I am using the row/record, as you say, not the name. Are you saying that as long as I do that, and render my field editor afterwards, it should be working with my display template fine? If so I must have a different issue.

Yes that should be working … must be a different issue.