Good afternoon,
I´m making some tests in may development environment to check how cachelookup property works. Well, i chose one table and made a query on it, that returns just one row, through AOT, using the fields from the PrimaryIndex, which was a unique Index and the table´s primary key also..
With the entiretable cache, i could see that just the first select went to the SQL Server using the profiler. The other ones didn´t go there, because Dynamics was retrieving them from cache.
When i change the table setting to Found, all my selects started to search the data in database, not just the first one. It is having the same behavior that the None CacheLookup (no cache). What could be wrong? I was thinking that with the found cachelookup, the row returned from the database in the first select would be cached in AX and the other ones would look for it in cache, the same way that it worked in EntireTable, not in database anymore.
Regards.