Removing the Ability for Users to Change the Column Layout for Detail Lists in Creatio (formerly bpm’online)

A built-in feature of Creatio is that all users can customize list/grid column layouts for the columns that are most useful to them. This can be done by clicking the three dot (ellipsis) button above the detail list and selecting “Setup columns” from the menu:

A system administrator can customize the layout for all users by choosing to save a layout for all users:

However, there are many valid times where you do not want users to be able to change a list layout and only want them to use the default layout defined for all users. Luckily, this is an easy task to do. We’ll need to open the detail schema, this is usually named by the detail wizard something like “UsrSchema2Detail” but the title of it will reflect the detail you’re looking for. Once opened, you’ll simply add the following to the methods:

getGridSettingsMenuItem: Terrasoft.emptyFn

The whole file, unless you’ve made other changes, will look something like this:

define("UsrSchema1Detail", [], function() {
	return {
		entitySchemaName: "UsrMyObject",
		details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
		diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/,
		methods: {
			getGridSettingsMenuItem: Terrasoft.emptyFn

With the one line of code added above, the “Columns setup” option will no longer appear on the menu and the user will not be able to change the layout. The approach here is the same for removing the add, edit, copy functions for the detail as well.

Want content like this delivered to your inbox? Sign up for our newsletter!

Ryan Farley

Ryan Farley is the Director of Development for Customer FX and creator of He's been blogging regularly about SalesLogix, now Infor CRM, since 2001 and believes in sharing with the community. His new passion for CRM is Creatio, formerly bpm'online. He loves C#, Javascript, web development, open source, and Linux. He also loves his hobby as an amateur filmmaker.

Submit a Comment

Your email address will not be published. Required fields are marked *