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!

Architect Forums - SalesLogix Scripting & Customization
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.

Forums RSS Feed

Back to Forum List | Back to SalesLogix Scripting & Customization | New Thread

View: Search:

Author

Thread: Contact.Account and Account.Account differeneces

joe
Posts: 26

Contact.Account and Account.Account differeneces Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 10 Dec 08 6:49 AM

Has anyone ran into the situation where these two fileds hold different data? I found 350 difference out of 26,000 possible contacts.

If so could anyone explain the reason for the redundancy of the Account column and how this happens. Additionally, what was your prefered method for updating the records.

You can run this SQL to see if you have any differences.
SELECT c.ACCOUNT as conName, a.ACCOUNT as accName, *
FROM sysdba.Contact c, sysdba.Account a
WHERE c.ACCOUNTID = a.ACCOUNTID
AND c.ACCOUNT <> a.ACCOUNT

[Reply][Quote]

RJ Samp
Posts: 973

Re: Contact.Account and Account.Account differeneces Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 10 Dec 08 9:23 AM

No idea what version you are running but I haven't had any problems with it.....

The reason for the redundant/denormalized Contact.Account (and no Opportunity.Account) field was to speed up/simplify groups, lookups, mail merges, contact processes...

One thing going on these days is developers using LookupEdit controls that allow for typing into the Text Field......SLX provider is more powerful these days (than say 6.1.x) and will store the data to the parent field if you are not careful.

Also scripts can change Contact.Account and not Account.Account.....

Update from other tables?

UPDATE Tablename
SET Tablename.Field = X.OtherField
FROM
(SELECT IDfield, OtherField From OtherTable Where......) X
WHERE
Tablename.LinkingFieldID = X.IDFIELD

UPDATE sysdba.CONTACT
SET ACCOUNT = X.ACCOUNT
FROM
(SELECT ACCOUNTID, ACCOUNT From sysdba.ACCOUNT) X
WHERE
CONTACT.ACCOUNTID = X.ACCOUNTID

[Reply][Quote]

joe
Posts: 26

Re: Contact.Account and Account.Account differeneces Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 10 Dec 08 9:30 AM

Thanks for the quick responce. We are using 7.01. I appreciate the SQL on how to update the tables, but I guess my question was really what should be the master name for the Account field. I decided that the account should overwrite what the contact says.

I will say that I think SLX has a bad practice here with the redundant/denormalization.

So once again I really appreciate the explanation of their logic even if I disagree with it in principle.

Thanks joe

[Reply][Quote]

Bob (RJ)Ledger
Posts: 1103

Re: Contact.Account and Account.Account differeneces Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 11 Dec 08 7:04 AM

Quote:

Originally posted by joe

..
I will say that I think SLX has a bad practice here with the redundant/denormalization.
...
Thanks joe

Disagree.....

If you think there's just a Account denormalization then you ar ein for aMAJOR shock.. it's all over teh place.. history table, etc... It's very normal practice and in fact we all (BP's) do it all the time as well.

MSCRM has it and you will find it everywhere.

It's normal DB practice to de-normalize data for efficiency, etc. "Normalized" databases are great in theory.. VERY BAD in reality.
--
RJLedger - www.slxwizard.com
rjlSystems

[Reply][Quote]

joe
Posts: 26

Re: Contact.Account and Account.Account differeneces Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 11 Dec 08 7:33 AM

Thanks for your thoughts. I truely appreciate them mr ledger.

[Reply][Quote]

Kris Halsrud
Posts: 88

Re: Contact.Account and Account.Account differeneces Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 11 Dec 08 9:12 AM

You will see these mismatches when you move contacts between accounts or do a merge. I asked SLX support about this a lonnng time ago and they said it was intended so you could see the account the contact used to belong to. Not sure about that answer as it seemed like a bug to me at the time but, none the less this is typically why you see these mismatches appear over time.

[Reply][Quote]

Timmus Agersea
Posts: 328

Re: Contact.Account and Account.Account differeneces Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 11 Dec 08 3:58 PM

I agree with RJL. Academically designed databases are unusable for customers given the query tools and design of the SalesLogix UI.

Timmus

[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 © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 8/27/2025 5:21:29 PM