Thread: Automated Extended Product Insertion

I have a set of products that contain data beyond what's defined in the database. My plan was to pull the set of data from a work table into a loop. Within that loop I would call for a product insert via an existing aspdnsf procedure. With the inserted product, I would get an identity that I would then use in the extended table containing the extra data.

First question, am I on the right track with this?

Second question, once I have the import done...I'll need to modify the add/edit product screen and the product xml package.

Are there any insights to expediting this? Any suggestions?

Thanks,

- Nick

BUMP Anyone possibly have any thoughts to share? Thanks.

A lot of this depends on the specifics of what you are trying to achieve.

As an example - I use the misc text field to hald an xml snippet something like this :-

Code:

<Data>
	<Delivery></Delivery>
	<DeliveryMax></DeliveryMax>
	<Old></Old>
	<field1></field1>
	<field2></field2>
	<field3></field3>
	<field4></field4>
	<field5></field5>
	<additionalinfo></additionalinfo>
	<msds></msds>
	<tech></tech>
	<video></video>
	<link1></link1>
	<link1text></link1text>
	<Social1></Social1>
	<Social2></Social2>
</Data>

It's then trivial to get at this data from your xmlpackage with either a modification to the query or an additional query.

You can also import this field from the normal excel import.


TTFN

BFG

I like that concept, but if we were to want to provide search functionality on those fields, it seems that it would be more ideal to have them as their own fields in a database table.

My plan:

1. Insert the base product obtaining the identity and then insert to the supplementary table using the identity as a foreign key.

2. I will then need to change how the product information is retrieve - specifically the data access to include the new fields.

3. Update the product display package to include the desired fields.

4. Update the product maintenance screen to include the supplement table - maybe as a separate screen from product?

5. Create a new add/edit procedure to record the data and changes...

Of course, import the data too...

If anyone has done this already, I'd be interested in paying for some consulting time to make this piece happen. I'm not interested in reinventing the wheel.