Image URL's instead of local file

[tmattar]

Is is possible to specifiy a url for an item photo instead of uploading one of my own? As an example, my supplier has a web server with all the latest photos of the product line. If i can specify his url to the large photo, then using imageresize I can also get the medium, and icon size photos.

Thanks

[modelpoint]

Is is possible to specifiy a url for an item photo instead of uploading one of my own? As an example, my supplier has a web server with all the latest photos of the product line. If i can specify his url to the large photo, then using imageresize I can also get the medium, and icon size photos.

Thanks

Absolutely. Just add a custom field to InventoryItem table (using data dictionary manager) that will hold your URL; modify the aspdnsf_GetProducts stored procedure to return this custom field and than modify XML packages to get image via your supplier webservice instead of using aspdnsf:DisplayImage

[ASPDNSF Staff - Buddy]

Instead of adding a new field to the Inventory table you should use the ExtensionData field in the Product table or the ProductVariant table. Then you can modify the aspdnsf_GetProducts procedure to return that field and modify the package to display it.

[modelpoint]

Instead of adding a new field to the Inventory table you should use the ExtensionData field in the Product table or the ProductVariant table. Then you can modify the aspdnsf_GetProducts procedure to return that field and modify the package to display it.

Do Product or ProductVariant tables even exist in ASPDNSF IS database? I don't see them.

[AspDotNetStorefront]

yes, they are just called different table names. We'll post more info here shortly.

[ASPDNSF Staff - Mark]

Do Product or ProductVariant tables even exist in ASPDNSF IS database? I don't see them.

The counterpart table of Product on IS database is InventoryItem.
At the moment, we don't currently support the ImageFileNameOverride feature, but this is already planned in the future release.

Meanwhile, you can use this workaround:

First, setup additional columns in the InventoryItem table so that you can map the individual images. You will use the custom field feature of IS for this.
There should be a column naming convention for this to work, i.e. :
ImageOverride_Icon = icon image
ImageOverride_Medium = medium default image
ImageOverride_Medium1 = medium 1st multiple image
and so on..

and then use the User role module to map the fields on the InventoryItem form.

You would then need to have the sourcecode to modify the logic for looking up images using the Image Override fields.
Please contact support@aspdotnetstorefront.com for this.

[modelpoint]

Meanwhile, you can use this workaround:

First, setup additional columns in the InventoryItem table so that you can map the individual images. You will use the custom field feature of IS for this.
There should be a column naming convention for this to work, i.e. :
ImageOverride_Icon = icon image
ImageOverride_Medium = medium default image
ImageOverride_Medium1 = medium 1st multiple image

Isn't that what I suggested to do in the first place? And by the way, you don't need any special column name convention for this to work.


You would then need to have the sourcecode to modify the logic for looking up images using the Image Override fields.

No, he does not need the source code. He needs to modify aspdnsf_GetProducts and aspdnsf_ProductInfo stored procedures to make the custom fields with image URLs available in the resultsets. You don't need the source code option for this.

[ASPDNSF Staff - Mark]

Isn't that what I suggested to do in the first place? And by the way, you don't need any special column name convention for this to work.


No, he does not need the source code. He needs to modify aspdnsf_GetProducts and aspdnsf_ProductInfo stored procedures to make the custom fields with image URLs available in the resultsets. You don't need the source code option for this.

This was the workaround we suggested to one of our customer that was looking for this functionality.

Cool, whatever works for you ;)