Hi Software Developer Guy (is that you real name?!? ),

This is actually the expected behavior. Let me try to explain what’s going on.

On a Skuid Model, pretty much anything that references a particular field on a particular record will be updated when any change is made to that field. So if you had a Table and a Field Editor which both reference the same Model and you edit a field with the Table, then you’ll see the change to that field immediately reflected in the Field Editor. This all happens on the client (your browser) without any need to go back and forth between the server (saving you a lot of time waiting for server responses).

As I’m sure you know, some fields in Salesforce are formula fields. Their values may be calculated from one or several other fields. That’s the case with your Name field - it’s calculated by concatenating the First Name and Last Name fields together. But that is occurring on the server, not in your browser. The only way to refresh that value is to send the value of your updated First Name to the server and then get the updated Name value back.

That’s exactly what’s happening when you click “Save”: Skuid is sending First Name to the server. The server then recalculates the value of Name and sends the updated Name field back to Skuid. Skuid detects that the Name field has changed since the last query and automatically updates any components which reference that field.

The good news is that there’s a fairly easy work-around. Rather than using FullName, use a Template Field with the following template:

{{FirstName}} {{LastName}}

Both FirstName and LastName will be automatically registered with the Model, allowing Skuid to update the template in real-time without the need to round-trip to the server:

Thank you for the response!!! Sorry for not completely understanding, can you help me understand the following: I understand the relationship between the Table and Field Editor, I think. They share the same model, correct? if they do then the values will be updated. Is that done through some event? Some Javascript. Also: My understanding is that you are only updating the model on the machine and not the server. Then when you hit the Save button all of the model is sent to the server to be saved. I don’t understand why a server trip needs to occur for the case of concatenated fields (such as name). With the Javascript I wrote, I was trying to mimic the first scenario. My understanding was that when a model.updateRow() occurred, then the snippet would execute. (Which did not need to go to the server). As the data is changed in the model only. I can kinda make this work using the console in my browser. if I do a model.updateRow() manually through the console, according to what I’ve seen and tested, it triggers the Script. However, how do you trigger the script when the user changes something on the First_Name__c box for example? Hope I made sense and that you can straighten me out. Software Developer Guy is an alias !!!

Ah… sorry I didn’t notice your custom field renderer before. Basically, the issue is that your field renderer isn’t registered with the Model, so Skuid doesn’t know that the UI field needs to be re-rendered when the Model field is changed.

Fortunately that’s not too hard to fix! All you need to do is register the UI field via the .registerField( UIField, ModelFieldId ) function. For example:

var $ = skuid.$,     field = arguments 0],     value = arguments 1];

 field.model.registerField( field, "FirstName" );

field.model.registerField( field, "LastName" );

 var firstName = field.model.getFieldValue( field.row, 'FirstName' ),

    lastName = field.model.getFieldValue( field.row, 'LastName' );

 skuid.ui.fieldRenderers.STRING.read( field, firstName + ' ' + lastName ); 

The image below gives you a sense of the difference between using the standard Name renderer, using a Template Field with FirstName and LastName, and using the custom renderer which has been registered with the FirstName and LastName fields (the example code above):

If you can use the Template Field, I’d recommend it. It comes with some awesome extra features, like the ability to edit the individual fields in a popup:

Hi, Thank you so much. That is what I was missing!!! I know it works, but there is something I don’t understand. I thought that when you dropped a field onto an editor, that field was automatically registered with the model. I guess that is not the case. Is there some documentation that you can point me to understand more of the squid sequence of events? Thank you.

Yes, the field is registered automatically, but only with one Model field - the “initial” field, if you will.

For example, if you have a custom renderer defined for the Name field, then the UI field will be registered with the Name Model field, but not the First Name or Last Name fields. So, a change to the First Name field will not be reflected in the Name field until you send the Model to the server and get a response back.

By registering the Name UI field with the FirstName and LastName Model fields, the UI field will be re-rendered when there’s a change to the any of the three fields: Name, FirstName or LastName.

Thank you that makes sense. That was the piece that I could not figure out.