![ideascale-icon.png]](https://help.ideascale.com/hs-fs/hubfs/ideascale-icon.png?width=40&height=40&name=ideascale-icon.png){kind=icon}
Enhancements to Data Calculation Logic for Accurate Community Activity Reporting
Changes applied to data calculation logic in Legacy (V1) and New(V2) Reporting
We have implemented fixes to ensure data consistency across Legacy Reporting (V1) and New Reporting (V2). These fixes ensure greater reliability and alignment between Legacy and New Reporting systems. Below is a summary of the issues identified and the resolutions applied.
1. Vote Retraction from Previous Dates (via API or Vote Upload)
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Functioned as expected.
New Reporting (V2): Vote retractions (vote count decrease) from prior dates were not reflected during the daily refresh (12:00 AM server time).
Resolution: New Reporting (V2) has been updated to correctly process and reflect historical vote retractions during the daily refresh.
2. Idea Vote Count when Idea is Moved to a Campaign with Different Funnel
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Vote counts were not resetting to zero when a campaign idea was moved to a different funnel campaign.
New Reporting (V2): Functioned as expected.
Resolution: Legacy Reporting (V1) has been corrected to reset vote counts appropriately when a campaign is moved to a new funnel.
3. Comment Vote Count when Idea is Moved to a Campaign with a Different Funnel
Impacted Data Sets: Comment Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Comment vote counts were not resetting to zero when a campaign idea was moved to a different funnel campaign.
New Reporting (V2): Functioned as expected.
Resolution: Legacy Reporting (V1) has been corrected to reset comment vote counts appropriately when a campaign is moved to a new funnel.
4. Submitter's Auto Vote-up Behaviour when an Idea Submitted on 'Behalf of', Moves to the Private Campaign, the Submitter is not part of
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions
Previous Behavior
Legacy Reporting (V1): Vote counts were not resetting to zero when an idea was moved to a private campaign where Idea submitter did not have permission to participate and 'Automatically vote on own idea' was ON.
New Reporting (V2): Functioned as expected.
Resolution: Legacy Reporting (V1) has been corrected to reset comment vote counts appropriately when a campaign is moved to a new funnel.
5. Import Ideas & Comments for Past Dates
Impacted Data Sets: All idea & comment stats
Previous Behavior
Legacy Reporting (V1): Functioned as expected.
New Reporting (V2): Events from prior dates were not reflected during the daily refresh (12:00 AM server time).
Resolution: New Reporting (V2) has been updated to correctly process and reflect historical ideas & comments during the daily refresh.
6. Vote Retraction for Real-time
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Vote retractions (vote count decrease) were not reflected during the daily refresh (12:00 AM server time).
New Reporting (V2): Functioned as expected.
Resolution: Legacy Reporting (V1) has been updated to correctly process and reflect the idea vote count during the daily refresh.
7. Idea Campaign Changed and Reverted to the Original Campaign
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Functioned as expected.
New Reporting (V2): When an idea returned to its original campaign after a campaign change, its original vote count was not reinstated.
Resolution: New Reporting (V2) has been updated to correctly reflect the idea vote count.
8. Idea Submission via REST API
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Functioned as expected.
New Reporting (V2): When an idea returned to its original campaign after a campaign change, its original vote count was not reinstated.
Resolution: New Reporting (V2) has been updated to correctly reflect the idea vote count.
9. A Regular Member Submits an Idea & later their Email Address is Associated with an SSO Identity
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Functioned as expected.
New Reporting (V2): When the member's identities were merged by the system, the idea count was not being merged.
Resolution: New Reporting (V2) would reset and show correct idea count once the member's identities are merged by our system.
10. New Idea Submission after 'Erase all Ideas' action
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Functioned as expected.
New Reporting (V2): The new idea count was not reflected. It was showing zero idea count
Resolution: New Reporting (V2) would reset the idea count to show the new idea count correctly.
11. Ideate Stage with Ideas within has 'Report Ideas as' label changed from 'Selected' to 'Implemented'
Impacted Data Sets: Selected and Implemented Idea counts
Previous Behavior
Legacy Reporting (V1): Functioned as expected.
New Reporting (V2): The change was not reflected in New Reporting (V2) when the 'Reported Ideas as' label was changed from Selected to Implemented
Resolution: New Reporting (V2) would update & correct the Selected ideas & Implemented ideas count
12. Login Count Drill Down/ Details
Impacted Data Sets: Login drill down
Previous Behavior
Legacy Reporting (V1): In the source table, only data from the past three years was available for drill-down views. However, in the stats table, charts were generated, which resulted in inconsistencies.
New Reporting (V2): Functioning as expected
Resolution: Legacy Reporting (V1) would now match drill-down data with chart data.
13. Label is Assigned to Draft Idea and Removed again.
Impacted Data Sets: Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Label assigned to Draft ideas were getting counted.
New Reporting (V2): Label assigned to Draft ideas were getting counted.
Resolution: Legacy Reporting (V1) & New Reporting would not take Draft idea labels into account.
14. Ideas are Linked to a Draft Ideas and Removed again via REST API
Impacted Data Sets: Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Linked ideas assigned to Draft ideas were getting counted.
New Reporting (V2): Linked ideas assigned to Draft ideas were getting counted.
Resolution: Legacy Reporting (V1) & New Reporting would not take the Linked ideas linked to Draft ideas into account.
15. A Moderator Tag is Added for an Idea and Removed Later
Impacted Data Sets: Moderator Activity Count
Previous Behavior
Legacy Reporting (V1): Moderator tag addition was counted but removal was not counted like it was for Tags and Labels.
New Reporting (V2): Functioning as expected.
Resolution: Legacy Reporting (V1) would now consider Moderator tag removal in the Moderator Activity count.
16. Purge/Merge Member
Impacted Data Sets: Total Members
Previous Behavior
Legacy Reporting (V1): Functioning as expected.
New Reporting (V2): Purged (deleted) or Merged member was counted in the Total members count.
Resolution: New Reporting (V2) would remove the Purged (deleted) or Merged member count
17. Members with Join or Register Request Pending
Impacted Data Sets: Total Members
Previous Behavior
Legacy Reporting (V1): Functioning as expected.
New Reporting (V2): Member with a request pending for joining a community or registering for the Workspace was not counted in the Total members count.
Resolution: New Reporting (V2) would count the members with a Join or Register request pending
18. Idea with Existing Votes, Move to Another Ideate Stage and is Voted on via REST API
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Vote counts were not increasing when the idea was voted on via REST API in the new Ideate stage.
New Reporting (V2): Functioning as expected.
Resolution: Legacy Reporting (V1) has been updated to correctly count the new vote
19. Multiple Upvote and Downvote on the Same Day
Impacted Data Sets: Vote Count, Net Activity Score, Engagement Actions & Engaged Members
Previous Behavior
Legacy Reporting (V1): Functioning as expected.
New Reporting (V2): The exact net votes count was not being calculated
Resolution: New Reporting (V2) has been updated to correctly calculate the new votes count
20. Nuke/Delete a member with a large contribution
Impacted Data Sets: All stats related to members
Previous Behavior
Legacy Reporting (V1): Stats with the member's contributions (like ideas, votes, comments, etc) were not being deleted.
New Reporting (V2): Functioning as expected.
Resolution: Legacy Reporting (V1) has been updated to correctly calculate all the stats related to members by removing the deleted member's contributions (like ideas, votes, comments, etc).
21. Ideas with Bad Data Showing Both Selected & Implemented Labels
Impacted Data Sets: Selected and Implemented idea counts
Previous Behavior
Legacy Reporting (V1): Some ideas were included in both selected and implemented labels due to previous bad data.
New Reporting (V2): Functioning as expected.
Resolution: The bad data has been fixed to show the correct idea counts for Selected & Implemented labels
22. Idea View Count Mismatch
Impacted Data Sets: Idea View Count
Previous Behavior
Legacy Reporting (V1): In the source table, some Idea view counts had no valid Member ID due to bad data
New Reporting (V2): Functioning as expected.
Resolution: The bad data has been fixed to only count Idea view with a valid Member ID.
23. Idea Share Count Mismatch
Impacted Data Sets: Engagement Action & Engaged Members
Previous Behavior
Legacy Reporting (V1): In the source table, some Idea share counts had no valid Member ID due to bad data
New Reporting (V2): Functioning as expected.
Resolution: The bad data has been fixed to only count Idea share with a valid Member ID.
24. Add or Remove label from Idea or Comment
Impacted Data Sets: Engagement Action & Engaged Members
Previous Behavior
Legacy Reporting (V1): The label count was not being updated correctly.
New Reporting (V2): Functioning as expected.
Resolution: Legacy Reporting (V1) has been fixed to update and correctly reflect the added/removed label count.