On a regular custom list field that is sourced, is...
# suitescriptm
Michael McNamara
08/28/2023, 8:45 PMOn a regular custom list field that is sourced, is there any way to append the list and add options? Example: List of employees filtered by transaction department = Employee department, but add two names that aren’t in the department? This is not a custompage. Or can expressions be used in a custom field filter?
c
Clay Roper
08/28/2023, 8:53 PMCan you source from a saved search that explicitly adds in the employees you want?
m
Michael McNamara
08/28/2023, 8:55 PMI cannot. Do not have the ability to use a search. Good idea though.
Michael McNamara
08/28/2023, 8:56 PMI tried using a client script:
billApproverList.push([{value: ‘1329’,text:‘John Doe’}]);
No luck
c
Clay Roper
08/28/2023, 8:56 PMWhere does this field appear?
m
Michael McNamara
08/28/2023, 8:57 PMOn a vendor bill. They wanted it filtered down to the same department on the record, but now want to add just two employees who are not in the same department.
c
Clay Roper
08/28/2023, 9:00 PMAnd you don't have access to update the sourcing on the field definition?
Clay Roper
08/28/2023, 9:00 PMOh, it's dependent on the department selected on the bill huh?
m
Michael McNamara
08/28/2023, 9:00 PMIt’s limited. I can’t seem to use expression for (OR Department = etc….etc.)
Michael McNamara
08/28/2023, 9:01 PMYeah
c
Clay Roper
08/28/2023, 9:02 PMIs that something a person could change while the bill is being edited?
Clay Roper
08/28/2023, 9:02 PMthe department that is
m
Michael McNamara
08/28/2023, 9:03 PMNo because it’s filtered already. They can’t select what’s not there. I did the script with fieldChange. Would postSourcing function be better?
c
Clay Roper
08/28/2023, 9:04 PMWhat I meant was: if there's a department field that's the source of the filtering for the employee field, can the department field be changed while the bill is being edited?
m
Michael McNamara
08/28/2023, 9:05 PMThat would make total sense in an ordinary world, but they want to keep the department on the record as is.
c
Clay Roper
08/28/2023, 9:06 PMHave you considered letting the field accept any employee and validating the choice using a map that includes the department plus the explicitly designated employees?
Clay Roper
08/28/2023, 9:07 PMusing validateField or saveRecord
m
Michael McNamara
08/28/2023, 9:07 PMYou gave me hope there for a second. I reied changing the department, adding the employee and then changing it back. It cleared the field. Ugh!
c
Clay Roper
08/28/2023, 9:19 PMCould you:
1. Make this field (#1) accept all employees
2. Add two other fields (#2, #3), one filtered by department and one that includes those two employees only (as an override)
3. Clear the value of #2 when #3 is changed and vice versa
4. Set the value of #1 to match what's selected in #2/#3, either when they change or on saveRecord
m
Michael McNamara
08/28/2023, 9:24 PMI will see if that works…
c
Clay Roper
08/28/2023, 9:29 PMGood luck!
m
Michael McNamara
08/28/2023, 9:29 PMThanks buddy!
Michael McNamara
08/29/2023, 2:03 PM@Clay Roper I found a workaround. I created a separate dropdown that could filter for those two employees. Then adjusted my workflow to use that field if the other field was blank. Thanks for your help!
✨ 1
c
Clay Roper
08/29/2023, 2:27 PMGlad to hear you got it solved!
2 Views