Name __Display name Category ---- -------------- -------- 22565422120 Gift Card Departments AW007-08 Black Diamond Quicksilver II Carabiners AW009-08 Black Diamond Quicksilver II SaleItems AW013-08 Petzl Spirit Adventure Works Catalog ...
Features need to be exported in a special format. Different products in a given catalog may have different features and even have different number of them. Azure solves this by requiring features as a comma separated list of name value pairs:
PSObject is a dynamic type that you can modify on the fly. First, I extracted a collection of features into a new Features property. Then I applied features to become new properties on the product object. CSV export will be able to pick it up transparently. I hope.
It should now be easy to export the list as CSV. There’s a caveat though.
Both ConvertTo-CSV and Export-CSV will happily export the list for you but will normalize every record to the common set of fields.
You won’t see the features in the list. Here’s a trick to get every product in the export have its own features:
Instead of piping the entire set to the ConvertTo-CSV, I basically processed the list one by one in the foreach loop. I also removed the type info and the CSV headers. Azure doesn’t need labels anyway. Works like a charm!
There’s one more thing that I needed to do for Azure Recommendations API to absorb the catalog. As you could tell, the catalog format is not exactly CSV. Every line can have different number of fields basically. Neither does Azure backend use CSV parsing to read it.
The double quotes in the export above were taken literally. Azure would think that the SKU # is "AW007-08", for example. And then the commas in the descriptions where messing up the parsing as well. My next post will be about the Recommendations API itself and I will write more about it, but here’s the final version that produces a clean catalog export ready to go: