I am running SugarCRM Professional, Version 7.2. I want to add a field to a layout in the calls module, but the field I want to add is a Studio created field from a different module. I searched the old Sugar vt bulletin forums and found lots of people talking about editing the php files and creating all kinds of relationships, but no one clearly said whether it can be done strictly via Studio. This site seems less techie, but I have not found an answer here either. Can I (without editing any source files manually or installing JavaScript files) make a field created for one module available for the layout of a screen in another? It sure seems like something lots of people would want to do. Thanks for any help I get (even if the answer is that it cannot be done).
The functionality you are looking to achieve can be easily achieved with Sugar Logic which is a formula-based engine akin to Excel formulas. Since Paul's example is looking for a specific use, I will highlight his use case in the steps to achieve this functionality:
Go to Admin > Studio > Calls > Fields > Add Field
Create a text field called lead_account_name and on that field creation screen, check the 'Calculated Value' box and then 'Edit Formula':
A formula builder window will pop up and on that pop-up, click the 'Related Field' button.
Once that is clicked, set the module to 'Leads' and the field to 'Account Name', and then click 'Insert'
This action will automatically create the necessary formula into the builder and then you can click 'Save' to return to the field creation.
Click 'Save' again to finalize creating your field
Remaining in Studio, go to Calls > Layouts > List View
Locate the newly created field in the far right column and drag it over to the desired location in the first column labeled 'Default'.
Click the 'Save & Deploy' button to publish the new layout.
Create a call associated to a lead and see that the list view displays the expected information!
With the above steps, you are all set to begin utilizing the new functionality. A couple notes towards understanding this feature:
This will only display data on records created or saved after the field is created.
While the example above deploys the field to the list view, you can also deploy the field to any other available view in the module.
If you implement a significant number of calculated fields using related formulas on a module, you can negatively impact the performance when saving or mass updating records as these formulas need to perform backend calls to the other module(s) to retrieve and update the data.
Using these calculated fields is best done when you are only expecting a singular relationship to exist between the two modules. For instance, if I created a call with 2 leads as an attendee on the same call, then the account name retrieved by the formula would be arbitrary. If you need to pull specific data from a related record when other related records may also exist from the module, a custom logic hook is recommended.
I hope this helps and please let me know if you have any questions!
...can negatively impact the performance when saving or mass updating records (includes importing via wizard and updating/creating via the API). Any other inputs on calc fields / logic hooks / workflow impacts on performance?
...can negatively impact the performance when saving or mass updating records (includes importing via wizard and updating/creating via the API). Any other inputs on calc fields / logic hooks / workflow impacts on performance?
