11/25/2024 11:23: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 general SalesLogix import and data migration topics. View the code of conduct for posting guidelines.
|
|
|
|
Scribe importing all the data it matches
Posted: 07 Aug 07 11:01 AM
|
I am using saleslogix v 6.1 and have connected Scribe via the Oracle driver to our Oracle database. I have set up the necessary steps to:
1. Seek a uniqueid number in the contact table
2. Insert a number of fields from another table which matches this uniqueid number on the contact table
Although this seems fairly straightforward I just can not get the DTS to import all the fields into the other table once it finds a match. What it is doing is importing all fields into all the contacts it matches?? |
|
|
|
Re: Scribe importing all the data it matches
Posted: 07 Aug 07 1:27 PM
|
By "uniqueid" do you mean the contact.contactid?
Assuning the field you are insering are in the contact table you need to...
-Do a SEEK step (which it sounds like you have) to find out if the record exists
-Then on the Match=1 results of the above seek, do and UPDATE step for the fields
|
|
|
|
Re: Scribe importing all the data it matches
Posted: 08 Aug 07 5:49 AM
|
The uniqueid is not the contact.contactid field - the uniqueid field is the Oracle uniqueid field which was added to the contact table.
I do not wish to insert fields in the contact table, I wish to first match the uniqueid on the contact table then if a match is found I want the DTS to insert the fields in another table (which is linked to the contact table by the contactid and also has the Oracle uniqueid field amongst others. |
|
|
|
Re: Scribe importing all the data it matches
Posted: 08 Aug 07 9:08 AM
|
| This could be done in a couple of ways. You could first add a seek step to lookup the Oracle or foreign key and assign the SalesLogix contactid to a target variable that is used in the actual update/insert step. Another way is to have a single step to update/insert to the extended table and use the function DBLOOKUP( TextSourceField, "S" | "T" | "I", "table", "lookup_field", "substitution_field" ) to lookup and assign the contactid. It would look like this DBLOOKUP( S1, "T", "Contact", "OracleID_Field", "ContactID" ). Just replace S1 with the actual source field and OracleID_Field with column name. |
|
|
| |
|
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!
|
|
|
|
|
|
|
|