8/28/2025 3:27:10 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 writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
Sync problem on main view table
Posted: 19 Mar 09 6:40 AM
|
I've got a client where we have a custom main view/table called "Relationship". This effectively creates a many to many between account and contact. This table is critical to how they function from a business perspective. The standard SLX Account/Contact link is relatively unimportant to them. When a new contact is created there is code to create a new relationship to that contact's account. The relationship table contains AccountID and ContactID.
When a new Contact and Account is created on the host database, the matching Relationship is not synced out. The creation of the relationship is correctly entered into the workgroup logs. If a new contact is created on an existing account the matching relationship IS synced correctly. When a either is done on the remote database the new relationship IS synced correctly back to the host. The only place it fails is New Contact and New Account created on the host.
I have tried disabling the code that creates the relationship, then hand creating the relationship (there are add/edit forms for creating relationships) immediately after the account/contact is created. This also does not sync. You need to move around SLX for a while, then come back for this to sync. I'd been hoping to just launch the Add Relationship form filled in already when the Add Contact/Account form closes, let the user click OK. I've tried putting the code on a button on the contact form so you can click it to create the primary relationship once the contact is created, again same pattern of sync failure.
This has something to do with it being a new account. If the account is brand new, the relationships created will not sync from host to remote. If the account is brand new on the remote, the relationship will sync back to the host.
I've got SLX developer support on this and they are stumped as well. I'm willing to go for a work around, but I'm not coming up with clever ideas. I have a suspicion that the sync is somehow looking at the AccountID in the Relationship table, and applying security to this when going to the remote. There is quite a bit of functionality and code around this table so I'm reluctant to change the name "AccountID" to something else.
Any clever ideas as to how to get new relationships on new accounts out to the remotes?
Maria |
|
|
|
Re: Sync problem on main view table
Posted: 20 Mar 09 9:17 AM
|
Are you creating teh records using:
A - Insert/Update SQL
OR
B - Recordset
99% of sync issues tend to be related to bad datatyping - especially datetime.... The data WILL go into the local (main or remote) db with no error but just does not sync.
That's why we use recordsets and not SQL.
--
RJLedger - www.rjlSystems.net |
|
|
|
Re: Sync problem on main view table
Posted: 20 Mar 09 1:13 PM
|
I am using a recordset for this insert. Also this syncs fine if done on the remote, and syncs fine if the relationship being inserted is not attached to a recently added account.
Any other ideas?
Maria |
|
|
|
Re: Sync problem on main view table
Posted: 20 Mar 09 2:54 PM
|
"I have a suspicion that the sync is somehow looking at the AccountID in the Relationship table, and applying security to this when going to the remote. "
Well no kidding, that's what sync is supposed to do.....
..you are using one of the magic words in SLX....ACCOUNTID....and unfortunately have to abide by how it will handle it.
We used to do a LogSetGlobalID on the ACCOUNTID, and the new OLE DB Provider is supposed to do that for you.....and I don't think you can override...
IN the past......
we created a StandAlone table that syncs to everyone (like ACCOUNTSUMMARY).
We stored an SLX_ContactID and and SLX_ACCOUNTID in each record.....and a few more fields that describe the relationship (phone, email, title, role, CONTACTNAME, ACCOUNTNAME, etc.).....
and don't have any trouble in, currently 7.22 with this system. Originally deployed in v. 3.13..... remember the Contact may not be on the Remote User's DB......and the Account may not be on the remote user's DB.....
|
|
|
|
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!
|
|
|
|
|
|
|
|