I’m looking for a simple functional way to remove disable certain items from a dropdown list; items that have been widely used in the past and are therefore still in use for records in the CRM.
I’m aware of how to delete an item from a list entirely via studio. This results however in empty values for records that use that particular dropdown item.
So probably the simplest would be to simply hide particular values from the dropdown list when the list is shown in the frontend (edit-view of the field), but SuiteCRM doesn’t entirely forget these values, and is therefore still able to properly display/interpret the legacy items in older records.
Looks to me like this would remove the hidden items from DetailView as well, which is not what I want.
Workaround:
=> I’d have to make a second version of the same field, which would refer to the custom function and use this version for Editview
=> I’d have to turn off Inline-Edit for the Detail- and Listview-version of the field.
Well so yes, I got it to work in principle. But it applies to search, list, detailview and editview. So no good for what I’m looking for.
(my suggested workaround makes no sense of course unless I then also add a logic hook to keep the two versions of the same field synchronized…
Any other ideas how to affect a dropdownlist ONLY in edit-mode of a dropdown field? (I just want to omit certain items from the list the user can choose from, without removing the item from the list entirely).
Ok, I was on the same track. Actually ma last question was about possible no-coding/configuration solution in studio. As this is not possible, I’ve had the same idea about solving it using secondary field and doing db migration of values.
BUT - Suite’s built in Workflow IS a no-code solution - all done in the GUI, as a regular user. That is no-code isn’t it - no PHP, no command-line at all?
