Add more columns to Source Quality (Internal) Report for SW/PE/TE Churn

Link to report: https://app.powerbi.com/groups/ab010874-305a-4728-8cdb-f7ea02d9e336/reports/7794e998-66d4-406c-930c-933866222062/ReportSection4e6c15315793747a7138?experience=power-bi

Platform Churn:

Cancel Date Filter (asuming this is the date the platform was cancelled by Tech Services): Default to Advanced Filtering, and "is on or after"

Churn Platform Filter: Default to desktop_cloud or online

Inside of table:

• There should be two dates in this table: SF Cancel Date (Customer_Left_Date__c) and the date the platform was cancelled by Tech Services (cancel_date)

• Add Root Company ID

• Add Company ID (TE) and match the SF Cancel Date (Customer_Left_Date__c), Customer Left Reason (Status__c), Customer Left Reason Category (Customer_Left_Reason_Category__c), and Assets Cancelling (Assets_Cancelling__c) to that. This ensures notes are being put on the appropriate childsite for Desktop. For Online, can we still match to Company ID instead of Company ID (TE)?

• Using Root Company ID, find the most recent churn case created (RecordTypeId = 0121I000000iSIRQA2, Category__c = Churn), and who it was created by (CreatedById). If there are no attrition notes, this tells us who to bug.

• (Can be handled in Excel if not possible) add a column for Needs Correction. If the platform cancelled is online, but assets cancelling does not contain Online or Online Home, it needs correction. If the platform cancelled is desktop_cloud, but assets cancelling does not contain Desktop Bundle or Cloud, it needs correction. Also, if the Salesforce Cancellation Date isn't in the same month as when it was cancelled by Tech Services, it most likely needs correction.

PE Churn:

related_pe_inferred_disabled_date: Default to Advanced Filtering, and "is on or after"

Inside of table:

• There should be two dates in this table: SF Cancel Date (Customer_Left_Date__c) and the date the platform was cancelled by Tech Services (related_pe_inferred_disabled_date)

• Add Root Company ID

• Add Company ID (TE) and match the SF Cancel Date (Customer_Left_Date__c), Customer Left Reason (Status__c), Customer Left Reason Category (Customer_Left_Reason_Category__c), and Assets Cancelling (Assets_Cancelling__c) to that. This ensures notes are being put on the appropriate childsite for Desktop.

• Using Root Company ID, find the most recent churn case created (RecordTypeId = 0121I000000iSIRQA2, Category__c = Churn), and who it was created by (CreatedById). If there are no attrition notes, this tells us who to bug.

• (Can be handled in Excel if not possible) add a column for Needs Correction. If assets cancelling does not contain Parent Engagement, it needs correction. Also, if the Salesforce Cancellation Date isn't in the same month as when it was cancelled by Tech Services, it most likely needs correction.

TE Churn:

te_dropped_date: Default to Advanced Filtering, and "is on or after"

Inside of table:

• There should be two dates in this table: SF Cancel Date (Customer_Left_Date__c) and the date the platform was cancelled by Tech Services (te_dropped_date)

• Add Root Company ID

• Add Company ID (TE) and match the SF Cancel Date (Customer_Left_Date__c), Customer Left Reason (Status__c), Customer Left Reason Category (Customer_Left_Reason_Category__c), and Assets Cancelling (Assets_Cancelling__c) to that.

• Using Root Company ID, find the most recent churn case created (RecordTypeId = 0121I000000iSIRQA2, Category__c = Churn), and who it was created by (CreatedById). If there are no attrition notes, this tells us who to bug.

• (Can be handled in Excel if not possible) add a column for Needs Correction. If assets cancelling does not contain Tuition Express, it needs correction. Also, if the Salesforce Cancellation Date isn't in the same month as when it was cancelled by Tech Services, it most likely needs correction.