Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Tuesday, May 7, 2024 
 
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 ThreadView:  Search:  
 Author  Thread: Strange issues at Remote office
Steve Knowles
Posts: 657
Top 10 forum poster: 657 posts
 
Strange issues at Remote officeYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 25 Oct 06 2:06 PM
fiogf49gjkf0d
I have a client that uses remote clients and a remote office. I have two intermittiant issues that I can' t put a finger on:
Issue one - a custom field was added to the opportunity detail screen to track a date. This works great company wide, but for two users at the Remote office they say the date doesn't take intermittiantly

Issue two - I have a fairly complex modification that tracks opportunity stages and writes a stage date to the opportunity - the stage dates appear in a tab so the salespeople can see when each stage was advanced. If a stage is pushed backwards, all subsequent stage dates should be erased. This works fine 99% of the time. But on occasion when a user at the remote office changes a stage backwards, the subsequent dates don't clear. I have test this on the production database for hours and can't make it fail.

I have rewritten the code twice because I didn't know what else to try, but the problem persists - failing about 1 out of 100 times - always at the remote office - and never for me.

I really have my doubts that it is the code causing the problem, but I can't rule that out. Has anyone had a similar experience or have any suggestions as how to troubleshoot this? I am not sure what to try next. This has been happening for a few months and I am running out of things to try. Thanks
[Reply][Quote]
Jeremy Brayton
Posts: 491
Top 10 forum poster: 491 posts
 
Re: Strange issues at Remote officeYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 25 Oct 06 5:13 PM
fiogf49gjkf0d
Have you tried looking in SyncErrors.txt on both ends to see if it's trying to synchronize incorrect data? The data may go in correctly on one end but because it doesn't sync out completely, it could bring some weird behaviour.

What about getting a copy of the remote database to test against? Restore it locally in your testing environment and work on it from there. It may be a SQL issue but if not you'll want to modify the database so that the sales client can access it. You want to be able to look at their data as they see it.

I also believe the code isn't the problem but it's really difficult to narrow down data as the cause. When I code a new customization data never becomes a problem due to the fact that there is no existing data in my dev environment or when data is created inside the customization, it tends to be 100% correct. The trouble comes when you introduce a customization to existing data because there may be data combinations you aren't checking for, or records may not be as consistent as they should.
[Reply][Quote]
Steve Knowles
Posts: 657
Top 10 forum poster: 657 posts
 
Re: Strange issues at Remote officeYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 26 Oct 06 10:52 AM
fiogf49gjkf0d
Great idea Jeremy. Actually I found enough info in failed transactions to contact tech support. Sure enough - defect 1-39711 - Trouble with null dates being sent from remotes to main office. Thanks for the suggestion - definately pointed me the right way. Always a relief to put a name to the problem.

SLX says there is a non-released hot fix they may release to me. If not, I am thinking of setting the date values to blank as opposed to null.. Is there a reason I should not do this?

Anyway, this is load off to have at least ID'd the cause. I knew in my gut it was not the code also, but couldn't narrow it down (plus I always dread poking around the sync transactions) so you pushed to bite the bullet on that.

Steve K.
[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 | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 5/7/2024 3:07:16 AM