How can I bind the lookup column configuration to the package?

Hi Everyone,

I'm currently packaging a custom lookup in Creatio and I need to ensure that the lookup column settings, as shown in the screenshot, are configured as the default display fields and sorted by the CreatedOn field.

Could someone guide me on the proper way to bind the lookup column configuration so that it can display correctly after installing the package in another environment?

I'm particularly interested in:
1. Where the lookup column configurations are stored (fields to display).
2. How to bind them properly during export as default configuration.

Thanks in Advance!

Like 2

Like

3 comments
Best reply

That is stored in SysProfileData, you'll see how to bind that to the package here: https://customerfx.com/article/including-the-default-column-layout-for-a-detail-in-a-creatio-package/

For a lookup, I believe the key is something like (where "LOOKUPOBJECTNAMEHERE" is the name of the lookup object):

"BaseLookupConfigurationSectionLOOKUPOBJECTNAMEHEREGridSettingsGridDataView"

Ryan

That is stored in SysProfileData, you'll see how to bind that to the package here: https://customerfx.com/article/including-the-default-column-layout-for-a-detail-in-a-creatio-package/

For a lookup, I believe the key is something like (where "LOOKUPOBJECTNAMEHERE" is the name of the lookup object):

"BaseLookupConfigurationSectionLOOKUPOBJECTNAMEHEREGridSettingsGridDataView"

Ryan

Hi Ryan Farley,

It works great, but how can we identify the record among the common records, as shown in the screenshot below? Also, why do duplicate records exist?

Thanks in Advance!

Ajay,

The one with an empty Contact value (the 3rd row in the screenshot) is the one that defines the default column layout for all users. 

Ryan

Show all comments