This post is for the most part organized into three questions/categories, and in summary, my questions are about the database structure behind NetSuite, and how to associate a custom record with a customer record so it doesn't create duplicates.
Details of my questions:
How would one get NetSuite to associate the material request records and customer records?-
I'm setting up a custom record that takes data from an online form and pushes it into the record. The problem is that in most cases, the customer already exists (with their own unique identifier established). One would think that Netsuite would automatically search new custom records and check with existing customer records(since it is the parent), and push out the custom record into the customer marketing subtab for materials requests(since this is the name of the chosen subtab under the marketing subtab that the fields are pushed out to - although really, the relational database behind it all must just contain a separate marketing/materials requests table, with the two linked by primary keys/unique identifying numbers/symbols/whatever).
How would this lack of field duplication in a given...group of records be implemented? -
The material request records really shouldn't contain redundant data like names, addresses, etc at all if the records are taken out of a relational database table. (Right now, all of the data gathered from these online forms is being plopped into the marketing custom record, including redundant fields - although it should only be sourced from the customer records - but then the issue is that sourcing isn't just a fun NetSuite term for checking custom records for certain existing fields in customer records, and then creating a new customer records only from the customer fields) The only thing is, then one bunch of data(ie. first and last name, email) should be used to determine if the person is in fact, the person represented in customer records by a unique identifier/primary key (which I beliiiieve is called an internal ID in NetSuite - not positive about this yet). Only then could the primary key be used in the materials request custom record to link the two record sets(or tables or entities or whatever) together.
Now onto more of my confusion about the relational db behind NetSuite -
So after that comparison took place, the marketing-specific data should only go in its marketing custom records' fields, and the customer-specific data would be used for comparison then update or...something... and the marketing record would somehow be linked to the customer record, presumably through the customer id and market record id (in the relational database, i'd assume that these two fields would be in a lookup table with the two id's as the only fields within that table, but I am not sure if Netsuite automatically takes care of this database structure somehow)