Rank: Member
Joined: 1/28/2008(UTC)
Posts: 14
|
I'm trying to import my product catalog directly into the SQL database. I have all the fields figured out except the Bvin field. To maintain the proper parent child relationships (which the import tool won't support if I understand correctly), I thought I'd use SQL Integration Services to do a Product Column Transfer/Transformation as appropriate and generate the Bvin outside of the admin (during the data transformation) so that i can designate appropriate entries in the Bvin field and maintain the proper parent/child relationships and hence, product varations.
Anyone know what the Bvin generation code is? ...or A better way to import a large catalog with parent/child relationships in tact?
Thx,
Kenton
|
|
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC)
Posts: 2,136
Was thanked: 1 time(s) in 1 post(s)
|
Bvin's can be any unique string. BVC5 uses a GUID string. |
|
|
|
|
|
|
Rank: Member
Joined: 1/28/2008(UTC)
Posts: 14
|
Well, that makes life easier. So, what was the rationale behind using a GUID as opposed to a SKU or Product ID or other unique identifier?
BTW, KP = Kenton but I can't edit my screen name in the edit profile control panel :(
|
|
|
|
|
|
Rank: Member
Joined: 11/5/2003(UTC)
Posts: 1,786
|
We use GUID so that you change change your product SKU without having to remap the entire database. In BVC 2004 you couldn't edit a SKU once it was created because we used the SKU as the primary key. Now with bvin you are free to edit the SKU as needed.
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.