05-26-2016 05:38 AM
After upgrading to ACT v18 a new field was added to the publisher database following the normal lock/edit procedure. After the field was added we put code behind (a simple age calculation) and in the main office (publisher) it works just fine.
However the remote cut database does not show any of the newly added custom fields. The layout shows the field location and name but the drop down to map the field to does not show the custom field.
The publisher database shows Primary Age (field) in the field list selection but the remote database only shows pickList67 and none of the "base" fields are there like the "prepared by" field. The remote database seems to have it's own list of fields in the drop-down.
All of those fields were in the publisher database before the cut was made so why are they not appearing in the cut database?
05-26-2016 09:41 AM
Are there any indications of errors in the sync log that's available after a sync has taken place?
You can also generate sync logs by running actdiag.exe Databases > Database Details List > Right click DB name > Database Reports.
05-26-2016 10:44 AM
No errors shown in those three reports but something did pop up that I did not notice before in the main database is 1.8GB in size while the remote-cut database is 966MB. It's missing almost 900MB of data.
05-27-2016 04:42 AM
The server database does contain a lot of extra information regarding sync, remotes, security etc so may well be a lot bigger than remotes. The best indicator if number of records should match if all records are set to sync.
Regarding problem field are you on ACT 18SP1? If not apply SP1 patch.
Use ACTDIAG to run repairs on both Master and Remote databases.
Create a new field and test if that syncs over.
05-27-2016 05:55 AM