davidknipe / performfeedstatus Goto Github PK

Thanks for your work on this tool, David.

We are in the process of launching our site with Perform. We recently upgraded to EPiServer.Personalization.Commerce 3.1.2 from 1.0.0 to try to overcome problems with generating the Catalog Feed. Previously, the feed was stored in Blob storage, and we could access it using the PerformFeedStatus library, or by looking up the blob id in the DDS and downloading the feed from Azure storage.
SELECT [String01] FROM [dbo].[tblBigTable] where storename like '%CatalogFeed%'
However, after upgrading to 3.1.2, it appears that the storage mechanism for the feed has changed. There is no CatalogFeedTokenStore that I can see in the DDS, and the PerformFeedStatus indicates that there are no feeds. The last message from the Export Product Feed scheduled job says that a feed was created succesfully.

Libraries:
EPiServer CMS 11.11.3
EPiServer Commerce 13.3.1
EPiServer.Personalization.Common 3.0.0
EPiServer.Personalization.Commerce 3.1.2
PerformFeedStatus 3.0.0 (though PerformFeedStatus.dll says version is 2.0.0.0)

Expected behavior:

1. Run Export Product Feed Scheduled Job
2. Open Perform Feed Status
3. Show feed that was generated

Actual behavior:
No feeds shown in Perform Feed Status

Thanks for your attention. Please let me know if there is any data I can add to this report, or any other steps I can take to troubleshoot.