Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 354 subscribers
  • Views 921 views
  • Users 0 members are here
Forum Actions
Related

Calculating Call Due Dates

Ruby Payne

I posted this in a different thread, but this is a new formula issue I'm having I need help on.

ifElse(
equal($keycontact_c,true),
addDays($last_call_date_c,
ifElse(equal(related($calls,"call_type_c"),"Account Management Call"),
30,
ifElse(equal(related($calls,"call_type_c"),"Account Management Attempt"),
7,
""
)
)
),
date("")
)

We want it so that for Contacts a Call Due Date is calculated from the Last Call Date when:

Call Type = "Account Management Call" a call due date is calculated for 30 days from Last Call Date

Or, Call Type = "Account Management Attempt" a call due date is calculated for 7 days from Last Call Date

If the Call Type does not match, the call due date should be left blank.  However, all Calls are being set to the same day as the Last Call Date. What is wrong with this formula?

Parents
  • 0

    Hi ,

    the issue you will face with SugarLogic is that the formula will be recalculated each time the call record will be edited / re-saved. If you have or will have calculated fields that are bound via SugarLogic to fields on other modules like accounts or contacts, the field will also be recalculated once those records are edited.

    Therefore I recommend to set up a SugarBPM with a start event according to your criteria (i.e. call type = "Account Management Call" AND status changes to "held"

     An action item follows that sets the call due date to 30d from now on.

    The advantage besides the aboves SugarLogic in calculation is, that you can run the SugarBPM on the first update only.

    I hope that helps!

    Bests

    Björn Canales Pfisterer

    Technical Support Manager

    provalida GmbH

    --

    https:/ww.provalida.de

    support ( at ) provalida.de

Reply
  • 0

    Hi ,

    the issue you will face with SugarLogic is that the formula will be recalculated each time the call record will be edited / re-saved. If you have or will have calculated fields that are bound via SugarLogic to fields on other modules like accounts or contacts, the field will also be recalculated once those records are edited.

    Therefore I recommend to set up a SugarBPM with a start event according to your criteria (i.e. call type = "Account Management Call" AND status changes to "held"

     An action item follows that sets the call due date to 30d from now on.

    The advantage besides the aboves SugarLogic in calculation is, that you can run the SugarBPM on the first update only.

    I hope that helps!

    Bests

    Björn Canales Pfisterer

    Technical Support Manager

    provalida GmbH

    --

    https:/ww.provalida.de

    support ( at ) provalida.de

Children
No Data