Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Silver Contributor
Posts: 1,262
Registered: ‎04-08-2009

SLX 7.5.0 Web Open Account/Contact problem

[ Edited ]

Hello All,


We have a customer using slx 7.5.0 LAN.

They want to have a look at the web client and so we installed 7.5.0 web referencing to the same db.

We installed web host restored the 7.5.0 project, built and deployed.

Web client openes up with the welcome screen.

When we click on account it sais:

Object reference not set to an instance of an object.


When we open Contact it sais:

Group xml load error


In both cases, we do not see the groups.


This happened with the admin user.

We then tried a different user and we could open the account entity, but not the contact entity.

It saisSmiley Surprisedbject reference not set to an instance of an object.


So this seems to be user specific.


Opportunity and Lead is fine.


We added to custom tables for the LAN area 1-1 in account/contact.

We added those entities as extension to account and contact in slx web.

Redeployed but get the same error.


I know that there are a lot of fixes in sp1 and sp2 and we will upgrade to this version in some time.

But at the moment they want to have a look at the client with there live-data.


Can someone give me a hint here?

Message Edited by apfingstl on 20.10.2009 02:13 PM
New Member
Posts: 1
Registered: ‎10-27-2009

Re: SLX 7.5.0 Web Open Account/Contact problem

We had the same issue when we migrated to the 7.5.0 web version from LAN.

It turned out to be because of the custom groups. 

When you sign up as administrator, you have access to all the groups. If one of them is defined with conditions not supported in the web client, you get that error.

When you sign up as a user, you only get the views you have rights too so that is why sometimes you do not get the error.

Create a user for test, and only assign the All Accounts group and you should be fine for testing.

If you have a lot of groups, you will have to check each of them and find the ones that are causing problems.

We had to re-design most of our groups due to the way we use the product.