Loading...
Loading...
The table: catalog_channel_analytics stores 1 year's data and is used for the "Popular Items used in 3, 6 or 12 months" option in widgets such as "Recent & Popular Items". This is the reason that the existing out-of-the-box archive rule on catalog_channel_analytics is set to archive records created more than 1 year ago (beginning of the year). The intent of setting the archive and destroy rule to read only is to support the functionality above and the data in catalog_channel_analytics will be available/consistent with the selected option.
Navigate to the following archive and destroy rule for table: catalog_channel_analytics/ar_catalog_channel_analytics. /sys_archive.do?sys_id=edc13bad53131010bddaddeeff7b12b3 /sys_archive_destroy.do?sys_id=38e37bed53131010bddaddeeff7b12e5 Note that there is a banner message - "This item is read-only based on its protection policy" and a user who does not have maint role is not able to edit/make changes to the rules.
If the concern is the long retention of Archive Catalog Channel Analytics [ar_catalog_channel_analytics] records as the archive duration is currently set to 731 days / 2 years, there are 2 workarounds. a. Create another archive destroy rule on ar_catalog_channel_analytics and specify a shorter archive duration b. Support can assist to modify the existing destroy rule (/sys_archive_destroy.do?sys_id=38e37bed53131010bddaddeeff7b12e5) and specify a short archive duration If the archive rule is to be modified, it will need to be consistent with the selected duration in the "Popular Items used in N months" in widgets such as "Recent & Popular Items" which may be changed by a user at any time. It is recommended not to modify archive rule so that the data in catalog_channel_analytics is available to support the selected duration.
PRB1699802
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.