I have a page where users need to be able to change a picklist to change the status of a record, such as “working”, “submitted”, etc. However, normal users shouldn’t be able to put it into the approved status. I know I can add a validation rule that says "if the user’s profile = x and the picklist value = “approved”, then throw error message ‘you can’t select that’ ", but the ideal way, of course, is to prevent a normal user from being able to select the “accepted” value in the first place. This seems like a perfect opportunity for a custom Skuid renderer! I’m thinking that in read mode the picklist shows the current value, but in edit mode it shows only values that the current user has access to based on their profile. Something like: if (field.mode == ‘read’) { skuid.ui.fieldRenderersafield.metadata.displaytype]field.mode; } else if (field.mode == ‘edit’) { /* if (profile != admin) { add picklist value ‘working’; add picklist value ‘submitted’; } else if (profile = ‘admin’) { add picklist value ‘approved’; } render picklist in edit mode */ } How would I do this (or create an equivalent or similar solution)? Bonus points: Maybe it can also prevent normal users from changing the status from “approved” to something else?
have you tried triple === in the lines
isRetailSales = (userSalesCategory == "Retail Sales");
and/or
if (isRetailSales && field.mode == 'edit') {
I’m no JS whiz but I think that first one might need ===
Also you might try inserting some console.log lines at various junctures. Like after isRetailSales definition, console.log('Is Retail Sales? '+isRetailSales), and maybe also after select.length to get the length of your picklist and make sure that is coming in right, and maybe also in the $.each loop, log the value of each picklist value so you can see what it’s capturing. That might help you find an error somewhere.
Hope that helps!
Jack,
THANK YOU! the issue was with the “==” was why the picklist was not rendering properly. When I changed to “===” the rendering is honored. I will remember this going forward with JS!
However now, the value is not saved. ‘Retail Sales’ is the only option therefore chosen by default (I assume). I checked the object data in the console and the value indeed is not saving.
I tried adding this line with no success. Any idea why the value is not being accepted?
select.append($('<option value="Retail Sales">Retail Sales</option>'));
You said it’s a dependent picklist, is the controlling picklist value set correctly? Is there a record type issue, with Retail Sales not valid for the particular record type you’re using? What error are you getting that it won’t save? I wouldn’t think your custom field renderer snippet would need to handle saving
The controlling value picklist value is set correctly it defaults to the correct value. There is not a record type issue and I am not getting any error on save.
I made the field required to see what happens on save and it saves with the first value in the picklist not the value that is being displayed.
So for example I am only showing “Retail Sales” based on the snippet. When I hit save “Account Sales - Institutional Sales” is the value being saved which is the first value in the picklist.
I’ve run into similar issues with picklists, particularly for reference fields, where it will default to a value I don’t want and shouldn’t even be available based on filters or security settings.
Is it possible in your use case to default the value to Retail Sales on the model via a condition or model action? Or, if you make it required, can you add None as an option so people have to choose one?
Also, I think it might work better to instead of removing all the values that don’t equal Retail Sales, use a render snippet that declares these are all the values of my picklist: ‘Retail Sales’.
Just had another idea that might be a way around this:
Add two picklists, one that renders if the running user’s Sales Category = ‘Retail Sales’, and one that renders if it doesn’t. On the retails sales picklist, you could override the metadata so that the only option is Retail Sales, and make it required.
Unless your field is in a table…
Jack,
Thanks for all the great ideas. Your first suggestion wouldn’t work for my use case, I tried your second suggestion without success. I have been working on this all morning trying to go the editing the picklist route, but the value wouldn’t save.
So, I adjusted my thinking.
If the user is a retail sales user I want to set their category automatically and they don’t really need to see the field on create. So I edited the script to do a row update. Attached the script to the save button. Now on every save if the user is a retail sales user then the category is set and I can hide the field from view for those sets of users.
Here is the final code
var params = argumentsu0], $ = skuid.$; var isRetailSales = l]; var userModel = skuid.model.getModel('RunningUser'), model = skuid.model.getModel('QuoteDetail'), row = model.getFirstRow(), userRow = userModel.getFirstRow(), userSalesCategory = userModel.getFieldValue(userRow,'AC_Sales_Category__c'), isRetailSales = (userSalesCategory === "Retail Sales"); console.log('Is Retail Sales? '+isRetailSales); // skuid.ui.fieldRenderersdfield.metadata.displaytype]yfield.mode](field,value); //var select = field.element.find('select'); var category = 'Retail Sales'; if (isRetailSales) { model.updateRow(row, { AC_Category__c: category }); }
Perfect! sounds like an even better solution, since it’s more streamlined for retail sales users. Great work!
Thank you for all your help today!
I ran into a problem when I created a picklist with only one value. For some reason the value was not being save when the model was saved.
I looked in the console and the value in the model under data[0].fieldname was getting set but the value in the model under changes[id].fieldname was not getting set.
I add some lines to my code to set the value in the changes array and that worked. Not sure if this is good practice or if there is a better way but it seems to work.
Note that if I didn’t check the typeof !==undefined I got errors in the console after the record was saved or when trying to cancel model changes or close the popup. Not sure why this code was getting run at that time but that seemed to fix it.
Suggestions of better code are certainly welcome.
var field = argumentst0],<br> value = skuid.utils.decodeHTML(argumentst1]);<br><br>if (typeof field.model.datat0] !== 'undefined') field.model.datat0].Endorser_Type__c ='Municipal';<br> <br>var picklistEntries = field.metadata.picklistEntries;<br> picklistEntries.length = 0; // if you don't do this, then the "real" values are already in the picklist and the code below will add duplicate values<br> picklistEntries.push(<br> { value: 'Municipal', label: 'Municipal', defaultValue: true, active: true }<br> );<br> <br> id =-1;<br> if (typeof field.model.datat0] !== 'undefined'){<br> field.model.datat0].Endorser_Type__c = 'Municipal';<br> id = field.model.datat0].Id;<br> <br> } <br> <br> if ( typeof field.model.changeseid] !== 'undefined' && id != -1) field.model.changeseid].Endorser_Type__c = 'Municipal';<br> <br> <br>// Run the standard picklist renderer for the given mode<br>skuid.ui.fieldRenderersrfield.metadata.displaytype]efield.mode](field,value);
Question along the same lines. I am a noob at code writing so it might have been answered and I haven’t realised. I want to remove picklist values depending on if a checkbox is true or false. i.e if checkbox is true keep picklist entry, if checkbox is false, remove picklist entry.
Thanks.
FYI for those using a custom renderer on a multipicklist that want checkboxes:
field.options.type = "CHECKBOXES";
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.