SugarCRM is now SugarAI! Read the announcement  

Details about this thread
  • State Not Answered
  • Replies 4 replies
  • Subscribers 322 subscribers
  • Views 147 views
  • Users 0 members are here
Related content from around SugarClub

Silly Question: Is there a way to remove the last interaction link from an account or contact record?

Bud Hartley

It may not be a good practice, but to create a new Account or Contact record, many of our users make a copy of a similar record and change the content of fields to make the record unique.

For example, they will copy an Account or Contact record that is attached to a Parent Account, and simply change some of the fields (like the name, phone number, email address, etc.) The benefit is that there are many other fields (especially custom fields) that are identical to the source record that don't require data entry (like the assigned user, team, and numerous custom fields).

The last interaction field for the source record is also populated. It isn't a "major" issue since that field is updated when a meeting or call is recorded for the new account or contact record.

Sometimes, there may not be a new meeting or call related to the new Account or Contact to update the link.

My Question: In the on-demand environment, is there a way to unlink the Last Interaction association?

Parents
  • 0

    Hi  ,

    The native Last Interaction field is strictly read-only (no ability to modify via Studio) and cannot be modified by stock SugarBPM actions. The only ways to reset that field to a blank value would be via a custom logic hook or via a utility like our Upsert BPM Essentials plugin. With Upsert BPM Essentials, you can use our Enhanced Change Field action in a SugarBPM process to modify any read-only fields:

    One thing I will note is that Sugar only has the Last Interaction field on Accounts and you referenced this functionality being on Accounts and Contacts. I recall you implemented a solution from a Sugar partner, enable, to track last activity. If the fields you are looking to modify are from that solution, it may be possible to modify those fields via SugarBPM.

    If the fields from that solution are listed in Studio and flagged as read-only, temporarily remove the read-only attribute. Then you can use the stock SugarBPM change field action to set the field to a blank value when new records are created and that field is populated. Once you have your SugarBPM processes configured, go back to Studio and re-enable the read-only attribute on the field. After the field is marked read-only again, the SugarBPM action will no longer show the field modification you configured within the action, so be sure to label the action clearly to inform admins of its 'hidden' purpose. I've regularly used this approach for modifying read-only fields where customers did not have Upsert BPM Essentials. 

    I hope this helps!

    Chris

    Co-Founder | SugarCRM's 2024 Global Outfitters Partner of the Year

Reply
  • 0

    Hi  ,

    The native Last Interaction field is strictly read-only (no ability to modify via Studio) and cannot be modified by stock SugarBPM actions. The only ways to reset that field to a blank value would be via a custom logic hook or via a utility like our Upsert BPM Essentials plugin. With Upsert BPM Essentials, you can use our Enhanced Change Field action in a SugarBPM process to modify any read-only fields:

    One thing I will note is that Sugar only has the Last Interaction field on Accounts and you referenced this functionality being on Accounts and Contacts. I recall you implemented a solution from a Sugar partner, enable, to track last activity. If the fields you are looking to modify are from that solution, it may be possible to modify those fields via SugarBPM.

    If the fields from that solution are listed in Studio and flagged as read-only, temporarily remove the read-only attribute. Then you can use the stock SugarBPM change field action to set the field to a blank value when new records are created and that field is populated. Once you have your SugarBPM processes configured, go back to Studio and re-enable the read-only attribute on the field. After the field is marked read-only again, the SugarBPM action will no longer show the field modification you configured within the action, so be sure to label the action clearly to inform admins of its 'hidden' purpose. I've regularly used this approach for modifying read-only fields where customers did not have Upsert BPM Essentials. 

    I hope this helps!

    Chris

    Co-Founder | SugarCRM's 2024 Global Outfitters Partner of the Year

Children
  • 0 in reply to Chris Raffle

    Thanks Chris, Once again, Upsert leads the way.

    It's not a "major" issue, and it's my personal obsession with having things correct. The annoying thing about this is the reports that show an interaction where one didn't happen.  Most of the time, a new account or contact has some interaction within a week or two and the field becomes "real".

    Bud Hartley | Cape Foulwind, NZ (and Oregon, USA)