Merging Records and Transaction Counts in Dashboards
| Merged Reviews | This method is used to combine multiple existing reviews into a single parent review. |
| Collective Review | This method allows multiple transactions to be handled under a single Review ID, typically used for bulk actions. |
When I merge records, do I lose transaction counts in the dashboards?
No, merging records does not result in losing transaction counts. Both merged and parent reviews will be accurately reflected in the dashboards.
What happens to the counts when I merge multiple reviews?
Merging reviews is typically used to combine multiple existing reviews into one, often as a clean-up effort. For example, if you start a review and realize another similar review is already ongoing, you can merge one or more reviews into a single “parent” review. In the dashboards:
- The Merged column will show 1 for the merged review.
- The Status column will display 1 for the parent review (the one it was merged into).
The transaction counts will still be accurate, showing that there were 2 transaction reviews in total, but categorized by their respective statuses.
What are Collective Reviews, and how do they affect counts?
Collective Reviews differ from merges. This method creates a single Review ID to cover multiple transactions at once, often used for bulk actions. However, this could lead to a loss in transaction visibility because:
- One Review ID represents multiple transactions.
- In this case, the dashboard may only display one review, even though it covers multiple transactions.