A week ago we ran into a situation where the users decided that they liked the full name to be 'Lastname, firstname' instead of the default which was 'firstname lastname'. This was an easy SQL update and everything automatically pushed out to the remote / offline users as desired.
Today I was asked to update a custom field (essentially doing what we did above but for business specific data). We could see the update online, but when we went offline the data was not there. It just happened that we also installed a new remote client today - that computer COULD see the data remotely for the same contact (even though the rest of the remote folks could not). I tried updating a few other non-custom fields with SQL - that did not push the updated records out either.
SO - to get the update to 'push out' to the users I 'updated' (no real change) the fullname field again. Everything pushed out like a champ.
SIDE BAR - interestingly enough MS has hidden the triggers & the system databases so I can not see which fields do what (which also is a bit interesting to me since I thought I could see anything on SQL 2005). But that is another issue that I will figure out in time.
So obviously FullName 'triggers' a change to the remote users and certain non-custom fields do NOT --- any ideas what other fields trigger the push?
Confused? so am I...
Today I was asked to update a custom field (essentially doing what we did above but for business specific data). We could see the update online, but when we went offline the data was not there. It just happened that we also installed a new remote client today - that computer COULD see the data remotely for the same contact (even though the rest of the remote folks could not). I tried updating a few other non-custom fields with SQL - that did not push the updated records out either.
SO - to get the update to 'push out' to the users I 'updated' (no real change) the fullname field again. Everything pushed out like a champ.
SIDE BAR - interestingly enough MS has hidden the triggers & the system databases so I can not see which fields do what (which also is a bit interesting to me since I thought I could see anything on SQL 2005). But that is another issue that I will figure out in time.
So obviously FullName 'triggers' a change to the remote users and certain non-custom fields do NOT --- any ideas what other fields trigger the push?
Confused? so am I...