Changes in how Record Types are represented on a Model at page load

I’ve noticed some changes to how Record Type information is represented on a model when a page loads. This’ll be easier to explain with an example, so bear with me.

I have a page that presents the Record Type field of a model, using the picklist renderer so that the user can select the correct record type. Depending on the record type selected, an additional field may be presented (conditional rendering), and there’s also a button that picks up the name of the record type and puts it into a URL that’s behind a button - essentially we redirect to another page and pass in the selected record type’s name. The default record type is selected automatically.

In the previous version of Skuid we had installed, upon page load, if I was to go into the dev console and log the result of skuid.$M(“Model”).data[0].RecordType.Name I would get the name of the Record Type. RecordTypeId would have the ID of the record type, and there would also be a RecordType property on the row, which would hold the selected record type details according to what was on the model.

What’s happening now is that with the default, the RecordTypeId field on the model is set, but the RecordType property is not. Select a different value, and the RecordType property will then appear correctly against the model, and switch back to the default, and it will be there. Logic (such as the conditional rendering and the parameter in the URL) will work. But not without selecting something else, and then selecting it again.

I don’t think this behaviour is intended, hence my raising this here. This may appear really picky, and to be honest, it is an edge case, but we’ve had to break what was a nice UI flow for users and insert an extra step for them to perform. Not to mention it took a bit of trial and error to work around!