Lost ability to select "Copy" on Contracts module

Hi Cecilia Hanson,

This is known defect 81527.

The workaround is a code level change. Have your host with file system access perform the following change:

Changing
SUGAR/modules/Contracts/clients/base/views/record/record.php line82

from
'acl_module' => 'Manufacturers',

to
'acl_module' => 'Contracts',

and running a Quick Repair and Rebuild solves the issue.

I hope this helps!

Hi Patrick McQueen

Thank you for your prompt response! We checked our files and found that the path SUGAR/modules/Contracts/clients/base/views/record/record.php does not exist in our instance. In fact, there is no file named "record.php" under the Contracts folder. If it makes a difference, our org is on prem. 

Please advise.

Thank you,

Cecilia

Hi Cecilia Hanson,

Note that the SUGAR part of that path is meant to represent your root directory and should not be included. I am surprised if modules/Contracts/clients/base/views/record/record.php does not exist in your instance.

Also Try:

custom/modules/Contracts/clients/base/views/record/record.php

This file is created and updated by Studio changes to RecordView.

Hi Patrick McQueen,

We were able to find the file to update. Turns out we were SSH'd into the wrong IP.... lol.

We updated the file <root>/modules/Contracts/clients/base/views/record/record.php and it was working in our dev instance. 

However, when we recreated our steps in production, the changes are not showing up. We have run Repair and Rebuild several times, cleared our cache, and tested in different browsers. Still, the change is not there. 

I did submit a ticket to SugarCRM Support for this per the suggestion of Björn Canales Pfisterer so I will report back to this thread when I make progress. 

Thank you both for your help! 

Cecilia

Hi Cecilia Hanson,

Are your Regular Users assigned to Roles? Are you using Role-based Views?

If so, keep in mind that the custom directory saves unique record.php for each Role with a unique view in:

custom/modules/Contracts/clients/base/views/record/roles/

In each roles' subdirectory, the record.php file will need to be updated with the described change in order for the users in those roles to see the effects of the workaround.

Changing the core file's acl_module line should protect future role-based views from inheriting the symptom.

I hope this helps.

Hi Cecilia Hanson,

Are your Regular Users assigned to Roles? Are you using Role-based Views?

If so, keep in mind that the custom directory saves unique record.php for each Role with a unique view in:

custom/modules/Contracts/clients/base/views/record/roles/

In each roles' subdirectory, the record.php file will need to be updated with the described change in order for the users in those roles to see the effects of the workaround.

Changing the core file's acl_module line should protect future role-based views from inheriting the symptom.

I hope this helps.

Hi Patrick McQueen,

This resolved the issue! Thank you so much! 

Cecilia