11/25/2024 3:21:59 PM
|
| |
| 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!
Forum to discuss SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.
|
|
|
|
Table Association Situation
Posted: 26 Nov 07 8:48 PM
|
I have a table called C_Opp_Products. It is not associated to another table, but does have a global join on oppproductID to opportunity_Products. The system seemed to perform fine like this, but recently I discovered that some of the records in the C_Opp_Products table are not syncing to the remote office - some are. About 2000 of 46000 are not syncing..
I am suspecting the fact that the C_Opp_Products table is not associted with another table (namely Opportunity Products) is causing the records not to sync.
I also suspect I am going to need to create the new table as a one to one off the Opp_Products table, migrate the data, remap the fields on the forms, recreate the groups and reports, cut new remotes.. Did I forget anything? Ouch
Does this seem like a likely scenario? Is there ANY way I can avoid this? Can I somehow create the association in the backend? Any other thoughts on how to minimize the damage and set this situation right?
I am pretty sure of the response here, but cant hurt to ask, right? Thanks |
|
|
|
Re: Table Association Situation
Posted: 26 Nov 07 9:57 PM
|
| The fact that some are syncing and some not is interesting. Have you worked out why? That's where I would start - and then work out what you need to do to make them all sync. Once you have that sussed, it's just a one-off case of getting the missing records out to the remotes. |
|
|
|
Re: Table Association Situation
Posted: 26 Nov 07 10:07 PM
|
| I should also mention this is a remote office that was recently recut. The records didn't end up in the remote either on the cut or in subsequent syncs. |
|
|
|
Re: Table Association Situation
Posted: 26 Nov 07 10:13 PM
|
I'm still wondering why some records sync and some do not.
But why not just take a deep breath, add the extra fields to the standard OpportunityProduct table, make whatever other associated changes are required and make things easy for yourself in future?
PP |
|
|
|
Re: Table Association Situation
Posted: 27 Nov 07 10:26 AM
|
You know, I have problems with bunches of records not syncing here and there. A large chunk of them are in the Opportunity table. I check the table, and all the right fields are filled in, and the security is correct for both the opportunity and account records. I can never tell why some of those records don't sync up. Luckily it's a remote office, and even luckier is that the remote office is on an extended LAN network (30 miles away, but the network has been configured like a LAN), so I can link the SQL servers and just directly copy the records from the main database to the remote database. I probably spent a few hours trying to figure out the problem, but never could. I really wish there was just a checkbox for the remote office that is labelled "Completely Replicate Database" - I just want all records to sync, regardless.
I have wondered if anyone else had problems with sync not transferring records that should have synced... Misery loves company  |
|
|
|
Re: Table Association Situation
Posted: 21 Feb 08 4:40 AM
|
Hi,
>I also suspect I am going to need to create the new table as a one to one off the Opp_Products table, migrate the data, remap the fields on the forms, recreate the groups and reports, cut new remotes.. Did I forget anything? Ouch
Is there an easier way to do this? My problem is, we have several tables not associated as they should be (they are not assiciated with any table but should be - most of them to account-table). Now if an account is deleted all those entries in these tables aren't deleted automatically, which sould be done if they are associated corretly, right?
Thanks |
|
|
|
Re: Table Association Situation
Posted: 21 Feb 08 10:19 AM
|
Marty the solution to your problem is to create a join that allows cascade deletes through the join manager (in architect, manage\joins) then your records will cascade delete as you would like them to.
Steve, regarding your problem, have you checked that:
1) the un-synced records actually did have a corresponding record in the oppproduct table
2) there is no seccodeid field in this table (in version 7 it is automatically added for you, if this was created pre-version 7, this wouldn't be a problem), if the seccodeid DOES exist, is it populated with anything and if so, is it populated with any records that users on that remote office can access (in other words, set it to 'everyone' if it isn't already)
I've never had issues where records were not placed in the remote database, whether they synced out or not, after a re-cut. I believe it is possible the data is there, or for those records it maybe isn't supposed to be there.
I'll be the first to admit though that I've worked with SalesLogix for almost 8 years and still see something new with it almost everyday! Good Luck!
EDIT: Steve I just noticed your last response was in November - did you ever find the problem? |
|
|
|
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!
|
|
|
|
|
|
|
|