Hi,

The entity you have requested cannot be located ('C6UJ9AXXXXXX')

Has anyone come across the following issue before? When going into a record (this can be account, contact or opportunity) occassionally the above error is shown. And just as magically it disappears again. Sometimes it can happen for ten records in a row then the 11th works and then so do the first ten. Sometimes a logout and back in is required. It is extremely erratic.

There is nothing in the event viewer apart from the error mentioned above.

I did have concerns it may be this SLX Cache Server thing so I have switched it off for now and will ask the users to monitor the situation, however has anyone seen this before and know what the issue could be?

Also, a bit of a twofer here, "Look For Matching Records". Does anyone have any tips. I am frequently (and again, very randomly) getting "Timeout expired" and once you get this the look for matching screen does not work (you just get 'Object not set to instance of an object') until you F5 the insert screen (at which point you will of course lose everything entered). I have never been impressed with this area of the product and the frustrating part of it is its very important to almost every customer I do an implementation for. The UAT log is always filled with issues on this screen....Sage please look at it for version 8 if you read this

Many thanks,

Nick

Looks like a bad contactID.....when was the last time you ran integraity checker on the Database? Checked for Duplicate CONTACTID, Blank CONTACTID's, Null CONTACTID's......

Reindex all indexes NIGHTLY in SQL Server.....

Hi was gettting this error on my environment and this was my bug:

In Account entity I creade a new field CustStatus. This field would not be usser accesible, it would be updated by an integration worker. Based on this field value I would have some logic on LoadPage event. I would get the above error messaje when the value of this field would ne NULL.

So my solution was to default the value to a non null value.

Hi,

I´m getting the same error in accounts. In my case is consistent: Only admin can see the records, the rest of the users are getting the error on the screen.

I saw old post saying that the error can be related with missing fileds. But I checked all the fileds on the database and compare them with the properties in AA and everything is fine. 

I'm trying to identify where is the problem.

HI,

Your scenario would suggest an invalid SECCODEID in one your child tables, ACCOUNTSUMMARY for example (or any other tables hanging off account).

Thanks,

Nick

This may be a completely different issue and it might have been fixed finally, but I'll toss it out in case it helps.

We ran into trouble with multiple teams who cannot see each others data. After a terriitory realignment was done I ended up with several issues like what you are discribing. The issue was that child tables were not always handled properly in the casscade process. This is related to how security is managed in slx provider and the web when ownership is changed in a parent table.

The clearest example is when a 1-1 join is involved and a seccodeid exists in both tables. The most obvious error you see in this case is an error on insert on the 1-1 record because the primary key already exists. Basically, SQL Server throws the error when the provider (which can't see the record) tries to create it. The simple fix is to drop 1-1 tables or drop the child seccodeid, but the larger issue still exists in the realignment tool and security layers. 

We ended up writing several sql scripts and placing them in the SlxDbChecker to validate parent ownership chains down to the children and correct should a missmatch be located.

I'm pretty sure the cascading of SECCODEID's is STILL broken in 7.5.4....

I found the problem in my case: The problem was with the views that SLX uses. Sevearal of them were not created during the upgrade and another one was incorrect (ERPTradingAccount_)