slxdeveloper.com Community Forums

The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!

Administration Forums - Synchronization
Forum to discuss SalesLogix synchronization and remote database management. View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to Synchronization | New Thread

View: Search:

Author

Thread: Odd Synchronization Question

Justin Kuehlthau
Posts: 24

Odd Synchronization Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 16 Nov 06 9:13 AM

Hello,

If for some reason, bad sync due to versioning issues, a remote database has an account and the main database doesn't, what happens if the versioning issues are fixed and the remote user then updates the account. Does the main database throw away the update or does it request the rest of the information from the remote database?

Thank you,
Justin Kuehlthau

[Reply][Quote]

Frank Chaffin
Posts: 475

Re: Odd Synchronization Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 16 Nov 06 9:20 AM

If an existing account is changed this will send an update statement to the host database. When the update statement is executed by the syncserver nothing will happen because there is no account in the host database to update.

Bottom line: the missing account will not appear in the host database.

[Reply][Quote]

R.J. Snyder
Posts: 8

Re: Odd Synchronization Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 17 Nov 06 10:57 AM

In case you are interested, here's a way to "recover" the missing account so that it appears in all databases with all of its subordinate records.

In the database that still has the account:
1. Create a new account. I use the name of the "missing" account with " - NEW" appended so that I can keep them straight.
2. Be sure all fields in the new account are blank, other than name. If any fields default, like account status, set them to blank or . If a field is required, set it to the value of the corresponding field in the "missing" account.
3. If you care about the creation information, set the creation date/time and user in the new account to the values from the "missing" account. You'll have to run SQL statements (through the OLEDB provider) using the new account ID to do this. For example:
update account
set CREATEUSER = 'U6UJ9A00003F',
CREATEDATE = '2006-05-30 6:09 PM'
where ACCOUNTID = 'A6UJ9A0009KX'
You can get the user ID for CREATEUSER with:
select USERNAME, USERID from USERINFO where USERNAME = 'Thomas Pynchon'
The account ID is on the Details tab of the new account.
4. Merge the "missing" account into the new account.
5. Remove " - NEW" from the name of the new account.
6. Sync all around.

[Reply][Quote]

R.J. Snyder
Posts: 8

Re: Odd Synchronization Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 17 Nov 06 11:02 AM

Quote:

If any fields default, like account status, set them to blank or .

The "or" was supposed to be "or None if it is a pick list".

[Reply][Quote]

Frank Chaffin
Posts: 475

Re: Odd Synchronization Question Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 17 Nov 06 11:41 AM

You might also want to check out the "Resynchronize Database" function in the Workgroup Admin.

[Reply][Quote]

Page 1 of 1

You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 11/25/2024 4:31:38 PM