We have ConnectRE running successfully, and field changes in Core are synching to RE.   Obviously, we have many more records in RE than we do in Core.  If the record exists in Core, then we've been making any record updates to Core, and then they get pushed to RE.  (Otherwise, if the record update is mistakingly made in RE, then ConnectRE will overwrite the update with old information from Core.)  For records that exist in RE only, then the record update needs to be made in RE directly.

I contact Customer Support to see if there was some easy way for Development folks to know when they receive an updated email address five years from now, for example, whether the change needs to be made to RE or Core.  Their answer is that they need to lookup the record in Core first to make the change there, and if the record is not found, then look up the record in RE and make the change there.  That seems really clunky to me, particularly for Development users that spend their day in RE and don't really have need to interact with the ONSuite otherwise.  Not only is a lot of extra clicks, but I'm worried that new information will unknowingly get overwritten if a user does't follow the above policy.

In a perfect world, perhaps RE fields would be greyed out for records that are linked with Core via ConnectRE.  At the very least, even if there was some ConnectRE linking symbol or other such indication to an RE user that the record is integrated with Core would be helpful in alerting them that a record update needs to be made in Core instead.  There's got to be a better way!