RTC not getting the last version of object

Lec11

Hello,

I have NAV 2009 R2 installation and the following problem. I modified an object on the development database and then imported in the production DB, but RTC keeps getting the previous version of the object.

I deleted the metadata, I recompiled, I restarted the service, I changed the metadata cache size to 0 in Custom Config file, but no change.

Can anybody guide me in the right direction?

Thanks!

Douglas

I would close the RTC session and start it again. Check that you're in the same DB that you imported your object into.

Lec11

That's the first thing I have done. But no result.

Another interesting thing: I studied this link http://blogs.msdn.com/b/nav/archive/2011/04/28/about-object-metadata-and-why-i-can-t-see-object-changes-in-rtc.aspx. I realised that on the development DB the broker was disabled, but my object changes were instantly seen in RTC. How is that possible?

deV.ch

Are these changes, page changes? Are there personalizations on the profile level (Configurations)? If so, try to delete these personalizations and try again.
If you stop (not just restart) and start your service tier (and webservice if installed) you will always get the latest version of your objects. Only personalizations could maybe overwrite your changes.

To your second question. From what i experienced it's not that easy with the broker... in some scenarios it need to be disabled to detect the object changes, and in some it need to be enabled... So (unfortunatly) checking the broker does not tell you for sure if you receive object changes or not.
Even if it pick up most of the changes, i experienced situatons where weird things happen during large posting routines, where not ever change to the code was picked up. Therefore i try to work without restarting services as long as everythign seems well but as soon as I experience strange results i restart the service, which in 99% of the cases solves them.

Johannes_Nielsen

In 2009 R2
I use Metadata in Customsettings.txt too.

To my experience.... it's a pain!

No but more seriously:
Most cosmetic changes apply after a Client Restart
Changes in code may require a Service tier -restart

That's my experience anyways.