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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Contract & Entitlement Restrictions

(0) ShareShare
ReportReport
Posted on by

Hi,

I'm hoping that someone can help us with this problem.  We've been using Dynamics CRM (on-premise and, more recently, online) for running our customer-facing helpdesk since CRM 4.0.  For the most part, the product has done a reasonable job.  Last summer, our CRM Online instance was updated and, all of a sudden, we couldn't associate contracts with cases when the account associated with the contract was different to the account associated with the case.  This had not been a problem before the update.  This functionality is important to us as we sometimes receive support requests from third-parties on behalf of customers and so need to be able to handles situations along the lines of "Person A from Company B called to log a case against Company C's contract".  I logged a support case with Microsoft regarding this and despite much backwards and forwards (and proving that a change had indeed occurred), was told that this was not a bug and would therefore not be fixed.

As much as we would like to use entitlements instead of contracts (so we can take advantage of the SLA functionality), we can't as the same restriction exists there also.

Does anyone know how we can overcome this problem so that we can support these scenarios?

Many thanks.

*This post is locked for comments

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

    I'd be grateful for any thoughts anyone might have regarding this.  We are likely to have to migrate away from CRM due to this restriction.  I logged feedback on Connect over a year ago but there still hasn't been a fix.

    Thanks.

  • Karsten Wirl Profile Picture
    4,477 on at

    One thought...

    Create a new Lookup on the Case to achieve your goal?

  • NJC1 Profile Picture
    on at

    Thanks for the quick reply.  That was Microsoft Support's recommendation also.  I didn't go for it at the time as we had a large amount of historic information in the existing "Contract" and "Contract Line" fields and I didn't want to switch to a new field name and mess up our dashboards, reports, etc.  In hindsight, I probably should have done that but was hoping that Microsoft would acknowledge it as a bug and fix it in a future release (which unsurprisingly hasn't happened).  I could then have gone back through our old cases and associated the correct contracts retrospectively and carried on as we had done for years previously.

    We've always wanted to use entitlements (so we could then use SLAs) but this restriction on cases logged by third parties prevents that.

    Appreciate your suggestion though, that does sound like our only option at present.

  • Verified answer
    Karsten Wirl Profile Picture
    4,477 on at

    Second thought...

    Upgrade the existing lookup with the new lookup via workflow or business rule? Maybe the system doesn't realize that.

  • NJC1 Profile Picture
    on at

    Thanks - how might that work?

  • Karsten Wirl Profile Picture
    4,477 on at

    When you enter a value in your new lookup, a workflow is listening to this field and "copy" the value into the old lookup.

    This is pure theory... I'm not sure, if that works.

  • NJC1 Profile Picture
    on at

    Oh I see, yes, that might work.

    The other idea I had was to amend the SLA entity to make it a bit more like the contract entity (adding a start and end date, value, etc.).  I understand in CRM 2016 that we can now link cases directly to SLAs without needing to go through entitlements.  Only problem is that it looks as if SLAs are read-only.

  • Suggested answer
    Karsten Wirl Profile Picture
    4,477 on at

    So now you have two possible solutions for your issue. Your idea is also good.

    It's hard to say which one will fit most your requirements.

  • NJC1 Profile Picture
    on at

    Thanks for your help.  I do just wish we could have our old CRM back though. ;-)

  • Karsten Wirl Profile Picture
    4,477 on at

    Sometimes we have the same wish... but on the other side, the new versions have many potentials. :)

    Maybe you can mark my answer as verified. ;)

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans