8/16/2025 7:27:19 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
Lookup errors on new Activites when looking up Tickets that have too many results.
Posted: 03 Dec 08 5:20 PM
|
I am having an issue with creating Activities where if I try to do a lookup on Tickets, I get an error (below). It appears to be directly related to the amount of records returned from the lookup. If I don’t type anything in the ticket>account lookup I get the error (100+K records)… If I type in ‘a’ for the tickets>account lookup I get the error again. (1.3K records). Now if I type in ‘y’ it pull back the list (11 records). If I type in ‘ab’ I get back 1 record.
So I was talking about the lookup for tickets on the activity screen selecting ‘Account’ for the ‘Lookup Tickets By’… If try the same thing on the Account lookup lookup on the Activity screen, I get no errors no matter if I type in something in there or not. So it appears that this is not something system wide, just with the ticket lookup.
So with that being said is there some kind of pagination or something that I should be looking at? Why would it be particular to just that lookup.
FYI: I did try profiling the SQL statements coming across and saw that it might be choking on the concatenated field for ticket number, be I changed the calculated field to just return the ticketed and still got the same problem. The rest of the SQL statement appears similar in both account and ticket lookups.
Can any one try this in a DB that has a boat load of tickets and see if this is just something paricular to my DB or a problem with Slx?
Here is the error that is displayed in the lookup window.
-------------
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Sage.SalesLogix.Web.Controls.Lookup.LookupHttpHandler.BuildResultTable(IList`1 results) +1984
Sage.SalesLogix.Web.Controls.Lookup.LookupHttpHandler.PerformLookup() +2323
Sage.SalesLogix.Web.Controls.Lookup.LookupHttpHandler.ProcessRequest(HttpContext context) +349
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +440
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +65
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|