Data Integrity Issues Related to Third-Party Applications
Collectively identify problems stemming from and develop solutions for data integrity issues related to third-party applications
- Goal 1: Create documentation for users, admins and orgs on how to solve data integrity issues resulting from third-party apps in Salesforce
- Goal 2: Identify problems and impact resultig from data integrity issues and develop actionable solutions
Nonprofit and education organizations
https://powerofus.force.com/s/group/0F97y00000009hdCAA/sprint-data-issues-with-integatrations
| Full Name | Team Role | Github Username | Working Group? |
|---|---|---|---|
| Don Miller | Group Leader | https://github.com/Donmill7 | Data Integrity Integrations |
| Maida Rider | Contributor | https://github.com/RiderM780 | Data Integrity Integrations: Duplicates |
| Micah Adler | Contributor | https://github.com/micah-adler | Data Integrity Integrations: Duplicates |
| Pranav Nagrecha | Contributor | https://github.com/PranavNagrecha | Data Integrity Integrations: Duplicates |
| Adam Lincoln | Contributor | https://github.com/adamlincoln | Data Integrity Integrations: Duplicates |
| Bryn Scott | Contributor | https://github.com/Rad-B | Data Integrity Integrations: Addresses |
| Theresa Gossett | Contributor | tgossett | Data Integrity Integrations: Addresses |
| Radhika Kosaraju | Contributor | https://github.com/radhik012358 | Data Integrity Integrations: Addresses |
| Umayal Ramasubramanian | Contributor | umayal1983 | Data Integrity Integrations: Addresses |
After problems are identified, pick one where you can offer expertise or extensive personal experience, and form a group of 3-4 others who feel the same. In your working group, identify one person who will be the "Synthesizer / Scribe" who will from the very beginning of the work be responsible for writing a well-formatted narrative or clean outline of the content you'd like to publish/share by the end of the sprint.
After some initial conversation and brainstorming, the group decided to choose two topics and split into one subgroup for each topic.
The Duplicates subgroup started a catalog of matching and duplicate rules for common use cases.
Duplicate solutions - completed but lacking links in Github: Videos, including one on flows
The Addresses subgroup started documenting methods for ensuring address standardization and completeness, including a comparison of NPSP-compatible tools (https://github.com/SFDO-Community-Sprints/Data-Integrity-Integrations/wiki/Address-Data-Integrity-Documentation).
We recommend creating a Wiki page for past Sprint Event volunteers (per Sprint), and that Sprints goals, accomplishments, etc. Here's a good example: https://github.com/SFDO-Community-Sprints/DataGenerationToolkit. If you prefer to add this information to the readme file, here's a good example of formatting you can use: https://github.com/SFDO-Community-Sprints/Admin-Skills-and-Nonprofit-Salesforce-Teams
Please replace with the tasks you team was able to accomplish during the Sprint event.
| Full Name | Team Role | Github Username | Working Group? |
|---|---|---|---|
| Enter persons name | Group Leader | fakeusername | |
| Enter persons name | Contributor | Enter working group name |
Please replace with the tasks you team was able to accomplish during the Sprint event.
| Full Name | Team Role | Github Username | Working Group? |
|---|---|---|---|
| Enter persons name | Group Leader | fakeusername | |
| Enter persons name | Contributor | Enter working group name |
- Documentation can be found in the repository links under accomplishments and in the wiki site https://github.com/SFDO-Community-Sprints/Data-Integrity-Integrations/wiki
- Power of Us HUB group "Sprint Project: Data Integrity Issues": https://powerofus.force.com/s/group/0F97y00000009hdCAA/sprint-data-issues-with-integatrations
Next steps for future sprnts:
- Data Integrity issues related to duplicates: Add the "what" and the "why" and make the documentation more useable so integrations can be managed better
- Data Integrity issues releated to addresses: Complete documention by expanding and refining it, continue testing tools and solutions such as Google MAPS, and review all NPSP integration options