web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Suggested Answer

SLA updates on case creation from D365 for Outlook, how to prevent it?

(0) ShareShare
ReportReport
Posted on by 5

We have SLA working great except when internal team member uses email received from client to create case record from Dynamics 365 App for Outlook. How can we prevent SLA from updating to Succeeded until actual email response is made?

I have the same question (0)
  • Community Member Profile Picture
    on at

    Hi clwmarsh,

    Maybe you can change Success Conditions in related SLA items to achieve it.

    pastedimage1648532400463v2.png

    Can you share some screenshots about sla item if possible?

  • clwmarsh Profile Picture
    5 on at

    Thank you for responding. It appears our setup is very generic. 

    pastedimage1648588484478v1.png

    What would you recommend adding?

  • Suggested answer
    Bassey Profile Picture
    9 on at

    Hi,

    Your first success condition states that when the Created On field contains data.

    This means as soon as the case is created, the SLA condition should be succeeded. (As soon as a case is created, the Created On field is populated).

    Please remove the first success condition highlighted in the image below.

    pastedimage1648639763450v1.png

    Let me know if this helps.

  • clwmarsh Profile Picture
    5 on at

    Hello. After removing the condition, I then receive a nullable object must have a value. I removed all and added back in manually, same error. What could be causing this?

  • Bassey Profile Picture
    9 on at

    Hi,

    Please did you deactivate the SLA before removing the condition?

    Perhaps you could share a current screenshot.

  • clwmarsh Profile Picture
    5 on at

    The system requires deactivation of SLA to edit SLA items. I think with the Created On filter, it is carried over to the configuration Flow, where the trigger includes 'createdon' as a column filter.

    pastedimage1648670638135v1.png

    pastedimage1648670711243v4.png

    pastedimage1648670777404v5.png

    Additional thoughts to consider. Really appreciate your input.

  • Bassey Profile Picture
    9 on at

    Oh, I think I have an idea why this message is displayed.

    Perhaps the Created On date is still on the flow.

    Please could you replicate this exact SLA but for a new record?

    Add the Created On field as a success condition, save and activate the new SLA.

    Then deactivate and remove the Created On field.

    Please do not delete the existing SLA that has this error message displayed.

  • clwmarsh Profile Picture
    5 on at

    That was my next thought. I'll do so shortly. Thank you for your guidance.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 27 Super User 2026 Season 1

#2
Encore Business Solutions Profile Picture

Encore Business Sol... 14

#2
Eugen Podkorytov Profile Picture

Eugen Podkorytov 14

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans