I'm working to import individual's product purchases.
Custom object: Purchase
Fields: Product, price, date purchased
Would this be a one-to-many or many-to-many custom object? Also, what field would be the link?
Strive to avoid many-to-many (2nd-level) custom objects because they are not available from Velocity.
Unless you have a need to separately maintain Product metadata (characteristics other than purchase price, which is more a property of the purchase than of the product) then just use a 1st-level Purchase CO.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.