Preview of Multi-Select Lookup Control for Creatio (Equivalent to Infor CRM’s Multi-Select Picklist)

If you’re migrating an Infor CRM system to Creatio, which is something Customer FX specializes in, one particularly difficult thing to deal with is what to do with multi-select picklists in Infor CRM. There’s no real reasonable equivalent in Creatio. What we often do is move these to their own detail in Creatio, but this becomes awkward for users, especially for systems where they used many multi-select picklists in Infor CRM and you end up with screens with an unreasonable amount of detail grids in Creatio. Not to mention that it breaks up the flow of the screen. A multi-select picklist is no longer near other related fields and instead below as a grid. The multiple-choice field from Creatio devlabs is a big step forward (especially with the new styling compared to older versions) since it allows you to display the detail like it’s a single field even though the values are being stored as multiple rows. This is a fantastic way to handle a few multi-selects here and there. But we’ve had customers with the number of used multi-select picklists approaching the hundreds, and setting each one up as a detail, even displayed like a multi-combo field, is overkill (not to mention that you also have to deal with migrating the data to the detail objects). For a lot of these scenarios, the selected values are wanted and used (in reports, etc) as a comma-delimited list anyways. For those cases, I’ve created an exact duplicate of the Infor CRM multi-select picklist.

It works exactly the same as the Infor CRM picklist, it’s a 100% reusable control, takes literally seconds to add to a page, and you’ll create just a single field in the object to hold the results.

When possible, going the route of using a detail is always a better option. This route, just like the Infor equivalent, is storing the selected text(s) in the field. If you change the lookup items, it won’t update the stored value – plus no options for multi-language support. However, for less-important multi-select fields where a detail is overkill, and no need for multi-language support, this route is a quick and easy win.