Skip to main content

I’ve noticed that the standard field renderer for picklist values does not take record types into consideration for New, Unsaved Rows.

The two images below best describe my problem, and I was wondering how I could make sure that the drop-down for “Description” is correct when a new Row is created?


A new, unsaved Row shows All Picklist Values
a8fbf1fb7201b0551a434936a1373b66f30bb1de.png

After the Row is saved and edited, only then is the correct list shown.
8b7389b97697ee152174800285f8995874b38527.png

The Conditions on the Table’s Model specify that the Row must be of the ‘MISC’ type. But it seems that the picklist values are correct only once the Row has been saved, and consequently edited again.

A regression was introduced in one of the recent versions of Skuid such that picklists were no longer looking to record type to filter available values.  This has been fixed in the 5.21 version that is now available on the Get the Latest Skuid Releases & Everything That Came Before page. 

Hi Rob,

Thanks for the prompt reply. I’ve upgraded to 5.21, but am still experiencing this issue for new, unsaved rows.

Does this happen for all users, or just certain users? Are you running this as an Admin?

This happens for all users, including Admin.

I’ve included another screenshot to help illustrate that New,Unsaved Rows do not have the correct Picklist values.
4277212db50edaa57cbd8addaa5b75ffe764bf4d.png

I’m guessing you have a Condition on your Model on the RecordTypeId field, where you’re setting the Condition Value to be the RecordType’s 15-digit Id, correct? If so, you’ll need to change the Condition’s Value one of the following:

(a) use the Record Type’s API / Developer Name, e.g. “MISC”, instead of the 15-digit Id. Skuid will translate the Developer Name into the 18-digit Id automatically behind the scenes. To find this, go to the Record Type’s detail page, and find where it says “Record Type Name” (not Record Type Label).
(b) use the 18-digit Id.

We know this is lame, we’re working on it. In the next release of skuid, you should be able to have a Condition on 15-digit and it should work fine, but right now, if you have the 15-digit, it won’t work.

Ah! That makes sense. I changed to the 18-digit Id and it works perfectly now. Thanks Zach.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings