|
|
|
Support for the Blue Alligator applications
You are not logged in.
I guess I'm missing something obvious but try as I may I cannot get Family Code buttons to show on SP
Have uploaded FamilyCodes.csv and Products.csv and populated both files. Have configured two buttons on cloud - what am I missing?
Offline
In the field mappings screen for the the product file type make sure that you've set up field mappings for the family code fields that are in your products.csv file. This is the link between the products.csv and familycodes.csv files.
Offline
OK that worked thank you. Now having uploaded an amended Products.csv to include stock details, I note the facility to order the items is now inactive. In other words the products show along with price and image but I cannot click to order them (it worked beforehand). Any ideas what needs doing now please?
Offline
The plus/minus buttons and quantity/price entry options only appear while creating/amending an order for a customer.
I suspect that you've selected the Produt Catalogues option from the home screen to access the products - this is an enquiry only mode so the order entry options won't be displayed.
Offline
All looking good and I'm very impressed with the application but I have now hit a major snag. We have approx. one thousand SKUs (including product with several colour options). Our data is exported from Sage in csv format OK, but our SKUs are in a format that causes a problem coordinating with the image file.
Our SKUs are in the following format; product type (31 for example) hyphen individual product (1234 for example) forward slash colour code (01 for example) - ie 31-1234/01 It is not possible to save an image file in this format because of the slash in the file. Thus to assign images to each product they would have to be keyed individually. This is way too time consuming and labour intensive to contemplate. Our entire Sage stock control system is based on this long established nomenclature so it's not an option to change the SKU format.
We intend to trial the system initially and then if working smoothly look to integrate with our sage back office system, so getting round this problem in a time efficient manner is fairly key to progressing.
Any ideas on how we might get round this?
Offline
While the filenames for product images are based on the actual product code by default, this can be overridden. There is a PhotoRef field mapping available for the products file type. This allows you to specify an alternate image name to use for a product. However, this does mean that this alternate name would need recording against each of your products in the CSV file.
How does your image filename relate to a product (e.g. for product 31-1234/01, what would your image name be)? Is the same naming convention used for all your images? If so, there may be ways to implement this naming convention automatically.
Offline
For the initial setup I've used the PhotoRef field, but had to manually enter each individual image filename, which is obviously not viable for our whole product range.
We don't presently photograph every product in every colour, so for product 31-1234/01 (01 being black, whilst we may also offer, tan and brown) the image reference will be 31-1234 only.
Offline
Are there any examples of the naming convention you've used for images where you have taken them for individual colours? I'm assuming these won't just be the first seven characters of the product code.
Once we can establish a logical naming rule it should be straightforward for us to implement an solution.
Offline
Multiple colour images of the same product are not the norm, so in the event of it being necessary, a secondary image file would usually simply be labelled '31-1234 brown' for example to differentiate it from an existing image that was in black and named 31-1234.
No convention exists therefore so naming such a file 31-1234-02 would not be problematic. However....it is unlikely that we would want to shoot every product in every colour certainly at present, so it is likely that we would just use image 31-1234 for products 31-1234/01, 31-1234/02, 31-1234/03 etc.
Offline
ok, if you're willing to just use references such as 31-1234 then we can implement the ability for you to set the photo reference up as the first 'n' characters of the product code (in your case, 7 characters).
Offline
Thanks, is that a chargeable item?
Offline
There's no charge for this.
We have now added this feature to the cloud account functionality. Please see the following topic for more information: http://www.bacapps.co.uk/forum/viewtopi … d=809#p809
In your scenario, you will want to configure the PhotoRef field mapping to pick up the product code from your uploaded data, then set the maximum field length of the PhotoRef field to 7. This will only map the first seven characters of the product code onto the PhotoRef field.
Offline
Excellent thank you.
Offline
| Apple, the Apple logo, iPod, iPod touch, iPad and iTunes are trademarks of Apple Inc., registered in the U.S. and other countries. iPhone is a trademark of Apple Inc. App Store is a service mark of Apple Inc. |