<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Evolution Systems &#187; Mass</title>
	<atom:link href="http://evolution-systems.co.uk/tag/mass/feed/" rel="self" type="application/rss+xml" />
	<link>http://evolution-systems.co.uk</link>
	<description>Web Development, Software Development and Linux Consultancy services</description>
	<lastBuildDate>Fri, 08 Aug 2025 09:18:44 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>SugarCRM &#8211; Remove Mass Update From A Built In Module</title>
		<link>http://evolution-systems.co.uk/2010/01/02/sugarcrm-remove-mass-update-from-a-built-in-module/</link>
		<comments>http://evolution-systems.co.uk/2010/01/02/sugarcrm-remove-mass-update-from-a-built-in-module/#comments</comments>
		<pubDate>Sat, 02 Jan 2010 23:02:05 +0000</pubDate>
		<dc:creator><![CDATA[Matthew Jakeman]]></dc:creator>
				<category><![CDATA[Matts Blog]]></category>
		<category><![CDATA[SugarCRM Development]]></category>
		<category><![CDATA[Mass]]></category>
		<category><![CDATA[Update]]></category>

		<guid isPermaLink="false">http://evolution-systems.co.uk/wordpress/?p=416</guid>
		<description><![CDATA[This quick post will show you how to remove the mass update field from a built in module in SugarCRM. This will also work for a module that has been deployed but it will not work properly for a module built using module builder. Well, it will work but as soon as you re-deploy the [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>This quick post will show you how to remove the mass update field from a built in module in SugarCRM. This will also work for a module that has been deployed but it will not work properly for a module built using module builder. Well, it will work but as soon as you re-deploy the module the changes will be over-written.</p>
<p>For the purpose of this we will use the Opportunities module and assume that it is this that we wish to remove the Mass Update panel from.</p>
<p>The first thing to do is create the file &#8216;view.list.php&#8217; in /custom/modules/Opportunities/views/  &#8211; If this path does not exist, simply create it and place the file in there.</p>
<p>Once that is done add the following code to the file.</p>
<p><code><?php<br />if(!defined('sugarEntry') || !sugarEntry) die('Not A Valid Entry Point');</p>
<p>require_once('include/MVC/View/views/view.list.php');</p>
<p>class OpportunitiesViewList extends ViewList<br />{<br />  function listViewProcess()<br />  {<br />  $this->lv->showMassupdateFields = false;<br />  parent::listViewProcess();<br />  }<br />}</code><br />
This will remove the Mass update panel from the module. To adapt the above code for other modules simply change the name of the class from OpportunitiesViewList to <Module Name>ViewList and place it in the appropriate directory.</p>
]]></content:encoded>
			<wfw:commentRss>http://evolution-systems.co.uk/2010/01/02/sugarcrm-remove-mass-update-from-a-built-in-module/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
