We are in the process of upgrading the web client from 7.5.3 to 7.5.4.  At the same time we are implementing our own, custom-made account/contact merge functionality.  I am noticing that any field values that are brought over from the source account to the target account still show the target account values even though the database has been updated correctly.  The web client doesn't get updated until I reset IIS on the server.  I am guessing that this has something to do with caching (either with NHibernate or the new Cache Server) and the fact that I am not using the SalesLogix entities or NHibernate for the actual merge.  Anyone run into this or have any ideas on how I can resolve this?  Thanks. 

We're having trouble with the Cache Server and customizations in the new SLX Mobile portal.......had to turn off the Caching Service (and it specifically is caching NHibernate stuff). Customizations work fine.....Jeff H. looking into this....

We're not having trouble with 7.5.4 withOUT the caching service installed/on.

Bottom line (while we wait for SLX to come up with an exact reason why Caching service is 'gumming up' the works).....turn it off......

Quote: Originally posted by Shawn Lawsure We are in the process of upgrading the web client from 7.5.3 to 7.5.4.  At the same time we are implementing our own, custom-made account/contact merge functionality.  I am noticing that any field values that are brought over from the source account to the target account still show the target account values even though the database has been updated correctly.  The web client doesn't get updated until I reset IIS on the server.  I am guessing that this has something to do with caching (either with NHibernate or the new Cache Server) and the fact that I am not using the SalesLogix entities or NHibernate for the actual merge.  Anyone run into this or have any ideas on how I can resolve this?  Thanks.

If you are not using Nhibernate/Entity Model you will get this problem regardless of the Cache Server. Nhibernate has caching mechanisms built in and you neded to to tell it if you update values it is looking at. I have had problems going to back to version 7.2 (i.e. before cache server) which have been a problem. You should only use direct SQL (I assume you using direct SQL in your customisations) to 'read' from the database, although Nhibernate should be used even for read operations as you can benefit from those mentioned cahcing mechanisms.

Thanks,

Nick

Thanks Nick.  I implemented an easy (albeit with a slight performance hit) workaround whereby, after perfomining the merge, I load the entity (Account or Contact), update one of the fields (modified date), and save it using the IPersistentEntity interface.  This, obviously, updates the cache.

An easier way to re-set cached entities is to issue an evict.  For example:

   Sage.Entity.Interfaces.IAccount a = this.BindingSource.Current as Sage.Entity.Interfaces.IAccount;
   Sage.Platform.EntityFactory.Evict<Sage.Entity.Interfaces.IAccount>(a.Id);

This will invalidate the cache and force the given entity to be re-loaded from the db the next time it is accessed.

Can someone tell me how to turn off memcache? When I remove the pertinent lines from the web.config I get an error when trying to log in.

You can simply stop the service.  If not founf, SLX reverts to caching nHibernate data in the session.  You will see a lot of noise in the event log when you stop this service, but everythign should work just fine.