Schema Sync, Definition has changed, etc

JDVyska

Question for folks. NAV 2017. I make a change to a table, say Job, and sync that one table immediately. Why is it, then, that the RTC client reports that the definition of the Sales Header has changed on Sales Order pages?

Am I missing something in how sync works these days? I have a vague memory that this might have to do with subscriptions.

SilverX

I am not an MVP, but I want to shed some light on this dark spot: This error occurs for objects that have a relation to the changed table (or at least objects showing data related to the changed table).
This applies to both TableRelation and CalcFormula.
This error occurs whenever a table to which a currently open table or page has a direct connection or an indirect relation is changed.

Assume you have Table A, Table B, and Table C. Table B has a TableRelation to Table A. You have open Pages based on Table A, Table B, and Table C. When you change Table A, you get the error for Page A and Page B, but not for Page C.

I hope this clarifies the connection.

My assumption is, that in case of a table change, all related table objects are invalidated to force some kind of object reload and to avoid inconsistencies.

SilverX

That was something I wanted to check for a long time. Because I faced the same issues since our upgrade to 2017. I assumed something like this but, be sure, I've checked this before posting. Of course this applies to every type of sync.

kvb

good question, my "like" is on the table

kvb

JDVyska wrote: »

Question for folks. NAV 2017. I make a change to a table, say Job, and sync that one table immediately. Why is it, then, that the RTC client reports that the definition of the Sales Header has changed on Sales Order pages?

Am I missing something in how sync works these days? I have a vague memory that this might have to do with subscriptions.

By the way, Jeremy do you have multitenant environment or single?

JDVyska

Single tenant DB.

janpieter

We have that a lot, it is mysterious. I have a habbit of hitting 'build server application objects' and synchronize all objects with force from the menu after changing a key table. This seems to decrease the problem however I'm clueless why this would be needed.

kvb

My guess was about multitenant environment but its not right as JDVyska answered..
So it is also a mystery for me...
I usually just restart the client and that`s really frustrating for customer to do this each time after importing just a single minor table.

Maybe our MVP`s know more about it?

SilverX

I am not an MVP, but I want to shed some light on this dark spot: This error occurs for objects that have a relation to the changed table (or at least objects showing data related to the changed table).
This applies to both TableRelation and CalcFormula.
This error occurs whenever a table to which a currently open table or page has a direct connection or an indirect relation is changed.

Assume you have Table A, Table B, and Table C. Table B has a TableRelation to Table A. You have open Pages based on Table A, Table B, and Table C. When you change Table A, you get the error for Page A and Page B, but not for Page C.

I hope this clarifies the connection.

My assumption is, that in case of a table change, all related table objects are invalidated to force some kind of object reload and to avoid inconsistencies.

kvb

That makes sense, thanks!

JDVyska

Welp, that makes the most sense. I might test it out, but that's entirely logical.

SilverX

That was something I wanted to check for a long time. Because I faced the same issues since our upgrade to 2017. I assumed something like this but, be sure, I've checked this before posting. Of course this applies to every type of sync.