Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Party List Field - Limited to 13-ish Contacts RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We seem to be getting the very descriptive "http 404" error when we add more than 13 contacts to the Required field on an appointment.   Can someone tell me if there is a limit to the length of the party type or specifically, the Required field on the appointment form, and if so, is there a way to increase the size?   Our users will frequently have meetings where there are more than 13 attendees and would like to log these in one activity.

    Tuesday, May 20, 2014 11:25 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Of course the simple answer is to create a custom N:N relationship between contact and appointment and store your attendees there. 

    But I am interested in this error.  This is a proprietary attribute type and MS doesn't say much about its' limitations.  They also do not let us use this attribute type in customizations, and this may be one of the reasons.  But, there doesn't seem to be any logical reason to limit the number of entries unless this field is based on a completely different SQL schema.   The other possibility is the HTML rendering engine in CRM is not equipped to deal with more than 13 entries.  The 404 implies that the web server is looking for a page or resource that does not exist.  When and where, exactly, are you seeing this error?

    Wednesday, May 21, 2014 1:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Your question got me thinking about precisely when we were getting the error and found that it works fine if you use the out of the box lookup to add the contacts.   Our users tend to use a custom "branch" entity we built that allows them to select a number of contacts and then create a new appointment.   It is this custom functionality that is causing the issue - we are currently in the process of isolating what is causing the error.   Thank you for the very quick response and inspiring a little more digging and troubleshooting.
    Thursday, May 22, 2014 5:22 PM