Escalation rule not working

SOLVED

Hi 

i have an escalation rule running on a view on the company table (a view joining opportunity and company data)

it is supposed to set a field on the company table but it doesnt seem to be working - when i run the rule sql trigger in SQL i can see results but the escalation rule doesnt seem to want to run

is there any issues with running escalation rules on views?

  • 0

    Hi SIG,

    No, I have often done this. Is the escalation service running? do other escalations trigger OK? Do you have any SQL Triggers on the company table that might be going against what you're trying to do?

  • 0

    CRM views need to have specific fields in them from the joined tables otherwise they may not work as expected. There is a KB article if memory serves, that tells you this. Fields like the main table ID field, created by, created date, updated by, updated date, timestamp, deleted field, etc., need to be included from every table that are joined. There may be more but it's been a while since I did a lot with CRM.

  • 0 in reply to Matthew Shaw

    Hi Matthew - thanks for the reply, yes the escalation service is running and other escalations are working ok, i do have a couple of SQL triggers on the company table but they dont go against the escalation rule that isnt working

  • 0 in reply to SIQ

    this is my escalation trigger:
    oppo_paidinfull_n is null and ( (oppo_invoicesentdate_n +60) < #T)   and comp_renewalun is null and Oppo_BookingType = 'MC' AND  Oppo_Status !='Cancelled'

    ive set the escalation to run on table opportunity and view vOppoCompany

  • +1 in reply to SIQ
    verified answer

    This shouldn't be any different but just try the following, I've just changed a few elements of your query. Intrigued to see if this affects it in any way

    oppo_paidinfull_n IS NULL AND DATEDIFF(Day,oppo_invoicesentdate,GETDATE())<60 AND comp_renewalun IS NULL AND oppo_bookingtype = 'MC' AND oppo_status <> 'Cancelled'

  • 0

    Build a new view with all your conditions in, on opportunity, so it's just a simple select the escalation is running. You'll be able to track this in the logs. Then have a simple action that tells you it's has worked and to take the notified record out of the view. eg: oppo_paidinfull_n = 1

    Also from memory the condition statement does not like carrage returns so the whole condition statement has to be on one line.

  • 0 in reply to Matthew Shaw

    thanks Matthew - that worked!