Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
> 
Cannot create a new Contract Line in CRM 4

Respondida Cannot create a new Contract Line in CRM 4

  • Monday, June 30, 2008 6:09 PM
     
     
    Sign In to Vote
    0

    Using CMR 4.0, our customer tries to create a new Contract Line on his laptop using either the CRM Outlook client or web client and he gets the error: "The requested record was not found or you do not have sufficient permissions to view it."

     

    If he tries the same operation while connected through a terminal server, the item is created just fine.

     

    Does anyone know what would cause this error and why it would not show up in the terminal server case?

     

    Not sure it's related, but we recently installed the CRM Email Router on the CRM 4 server...

     

     

All Replies

  • Monday, June 30, 2008 7:51 PM
     
     
    Sign In to Vote
    0

    Same user with the same login credentials? 

     

    That is a bizarre one, the error your are getting typically relates to the lack of access to some related record like the account, contract, or an invoice.

     

     
  • Sunday, July 13, 2008 1:54 AM
     
     
    Sign In to Vote
    0
    I get the same error if I add a product to a contract line via the lookup (magnifying glass).   I don't get the error if I use the form assistant to add the product to the contract line.
     
  • Monday, July 14, 2008 3:37 PM
     
     
    Sign In to Vote
    0

     

    brandondoxtek - Did you find a solution to this problem?  I am having the exact same issue where I can add a product just fine using the form assistant but I get a permissions error using the lookup.  Seems pretty lame-O to me.
     
  • Monday, July 14, 2008 7:07 PM
     
     Answered
    Sign In to Vote
    0
     TB16 wrote:

     

    brandondoxtek - Did you find a solution to this problem?  I am having the exact same issue where I can add a product just fine using the form assistant but I get a permissions error using the lookup.  Seems pretty lame-O to me.


    We're just using the workaround for now.  I haven't opened a ticket with MS support yet.  I agree, it's pretty lame-O.

    Another option that I remember reading about that works (haven't tried it myself) is to add your own custom field to the contract line entity which does a product lookup.  Then remove the default product field from the form.