
02-09-2012 09:31 AM - last edited on 02-09-2012 09:49 AM
Yes, I know we're behind, but we just upgraded our web environment to 7.5.3 HF09 (from 7.5.3 HF01). Each hotfix was applied one at a time, and all prereqs were met (including lan HF20 for web HF09). In dev, there's a few oddies that are occuring that I'm hoping someone can help us out with. I'd like to try to address these one at a time, as perhaps we've missed a step that will have a cascading resolution to other similar errors.
Account Filters are sporadic, at best. Some standard filters, like "Account Manager" work, if they're the first accessed. Other filters, like a User-Lookup filter added to Address.Postalcode fail to apply at all. In the event log, for when a filter fails to apply, we see errors like this:
Exception caught during the processing of a message
Verb: POST
Uri: http://slx-dev-01/slxclient/slxdata.ashx/slx/crm/-
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeExceptio
at System.ThrowHelper.ThrowArgumentOutOfRangeExceptio
at System.Collections.Generic.List`1.get_Item(Int32 index)
at Sage.SalesLogix.Client.GroupBuilder.LookupFilter.A
at Sage.SalesLogix.Client.GroupBuilder.GroupInfo.getG
at Sage.SalesLogix.Client.GroupBuilder.GroupInfo.getG
at Sage.SalesLogix.Client.GroupBuilder.GroupInfo.getG
at Sage.SalesLogix.Client.GroupBuilder.GroupInfo.get_
at Sage.SalesLogix.Client.GroupBuilder.GroupsRequest.
at Invoke59a9f31522ff4f1c8f7645ee76e080fe.Invoke(Obje
at Sage.Integration.Messaging.RequestTargetRegistrati
at Sage.Integration.Messaging.Request.Process(Request
at Sage.Integration.Adapter.AdapterController.RealAda
at Sage.Integration.Adapter.AdapterController.RealAda
at Sage.Integration.Adapter.AdapterController.Process
02-09-2012 09:41 AM - last edited on 02-09-2012 09:52 AM
When I load the URL directly via Chrome or IE
http://slx-dev-01/slxclient/slxdata.ashx/slx/crm/-/groups?family=ACCOUNT&name=All Accounts&format=json&meta=true&start=0&limit=150
I do receive the metaData on screen.