Skip to main content
小组

SFDO Open Source Contributors

This group is home to Open Source Commons, and all who contribute code, configuration or documentation to the Salesforce.org suite of products, NPSP, Volunteers for Salesforce, EDA, etc. Read our earn all about our efforts in creating a sustainable open source community with best practices, guidelines, and technical tooling like CumulusCI, MetaCI and MetaDeploy: https://powerofus.force.com/s/article/SFDO-General-Info#Open_Source_Commons_(OSC) We welcome all those who wish to actively contribute to the conversation as well as the community. - Got a project you're working on? Great! Post about it here and share it with the Hub. - Want to volunteer your time with an existing project? Amazing! Post here and join a team. - Want to join the conversation about our Sustainable Open Source future? Awesome! Post your thoughts and spark a new conversation.

When it comes to your Salesforce org, you know how important data is. But for many, it can be difficult to organize, manage, and extract the information needed without the proper tools and resources. 

 

That’s where Declarative Lookup Rollup Summaries (DLRS) comes in.  

 

Declarative Lookup Rollup Summaries (DLRS) is a community-built and community-maintained open source Salesforce solution supported by the Salesforce.org Commons program. This managed package helps administrators who need to understand relationships between different sets of data in a number of situations, like when Salesforce Roll-Up Summary Fields aren’t an option or custom coding isn’t possible.  The DLRS Community team has been hard at work over the past months and just released the first major version as part of the Commons. 

 

Learn more about the app's history, highlights from the new version (2.17), and find out how you can contribute to DLRS today.

 

@Commons Project: DLRS

@Nonprofit and Education MindShare

@SFDO Open Source Contributors

@Salesforce.org System Administrators

@Salesforce.org MVPs

@Salesforce.org Customer Success

@Salesforce Administrators & Developers

@Customer Success Trailblazer Community Team

0/9000

We are so thrilled to share this new episode on the Salesforce Developer Podcast featuring @Aaron Crosman and all things #Snowfakery & Data Gen!  Give it a listen and leave Aaron some kudos in this thread!

https://developer.salesforce.com/podcast/2022/04/episode-119-open-source-and-data-generation-with-aaron-crosman

5 条评论
0/9000

Happy 2022 Contributors! Will you take 10 mins to share feedback about your Open Source Commons (OSC) contribution experiences in our brand new survey?

 

That’s right, I’m kicking off a fresh new year with a brand new survey! For the first time ever, we are launching the Open Source Commons Contributor survey to better understand the impact the OSC has had on you as an individual and on the Salesforce.org community at large. Your feedback will help us improve the OSC program, how we support and engage with the community and contributors, and will be completely anonymous. Aggregated results and responses may be shared internally and through external social channels.

 

If you’ve attended a Community Sprint or Mini-Sprint event, or volunteer your time on a project team, please take 5-10 minutes to complete the survey by Friday, January 21st!

 

Happy 2022 Contributors! Will you take 10 mins to share feedback about your Open Source Commons (OSC) contribution experiences in our brand new survey?

 

@SFDO Open Source Contributors

@CumulusCI (CCI)

@Commons Project: DLRS

@Commons Project: Data Generation

@Commons Project: NP SF How-to Series

@Commons Project: DEI Framework

@Commons Project: Grassroots Mobile

@Commons Project: Ombudsman Cloud Care

@Commons Project: Summit Events App

1 条评论
0/9000

On 20th/21st October our Animal Shelter Starter Pack app was available as a project in its first Open Source Community Sprint (AMER).   We had a few people sign up, and some good information was gathered regarding documentation, improvements and roadmap, so we will be looking through these, and hope to do a release next year.

 

Unfortunately, we are still yet to find a Community Lead for the project for it to move forward completely as an OSC project, and push the application forward to its full potential.  If you are interested in being that leader, please let us know.

 

Thanks

Chris

2 条评论
  1. 2021年11月29日 22:22

    Hi @Chris Rolfe this sounds like a great project to be part of. I am happy to volunteer. I am a Salesforce Admin and have experience in NPSP. Let me know If I can be of  assistance. My details are on my linkedin profile (https://www.linkedin.com/in/malikas/) but happy to email you my resume if it helps.

     

    Thanks,

    Malika

0/9000

@Jason Lantz and @Dave Manelski - One of the things that escaped my notice in Winter 16 until I took the usual renewal exam appears to be the GA of editing Audit Fields via API with System Permissions.  Previously, this was a request to Salesforce.com support.  This means that using tools such as Data Loader and DemandTools, we can now import data with historical dates without having to jump through hoops, so, yay.

 

I'd toss this on GitHub, but thought it might make an interesting discussion here: What do you think of adding System Audit fields to the NPSP Data Importer for all it's Objects?  This might require refining the tool a bit more, since if it truly becomes a proletarian item (as I'm personally hoping it might for power users - *cough* Custom Permissions Fix *cough*), not every User will have the ability to edit Audit fields.  Also, I'm not sure how API availability relates to the Apex behind the tool, so I'm honestly not sure it's even possible.  

 

Thought I'd ask and see what you and others thought.  Good/useful? Evil/destructive? Somewhere in-between?

13 个回答
0/9000

GitHub Help Needed!

 

In preparation for the PMM + V4S mini sprint (register here) we are looking at using Metecho!

 

Metecho will also to manage our project development declaratively (for the most part). That is where are looking for support in managing the GitHub side. Here have some experience with managing branches and branch merging is needed. You don't need to be an expert and you don't need to fully know this project!

 

If you want to volunteer please comment below.

17 条评论
0/9000

The @Commons Project: Data Generation​ team has been hard at work creating resources for generating test data. After all, what good are sandboxes without meaningful data? Today, we are delighted to share this blog post that the Admins team was generous enough to publish with us! We hope you'll enjoy this method for creating datasets for new staff onboarding using #Flow​ . If you try it out, we'd love to hear from you!

 

https://admin.salesforce.com/blog/2021/how-i-solved-this-populating-sandboxes-with-flow

admin.salesforce.com

10 条评论
0/9000

Heads up: The next release of CumulusCI, currently scheduled for April 29, will include a potential breaking change that may affect you if you use heavily customized release flows.

 

If you have custom flows that utilize the `github_release` task, they will need to be updated to include the `package_type` option (which is required). This change allows us to support 1GP and 2GP products on equal footing and without changing installation behavior.

 

If you are using CumulusCI's out-of-the-box release flows, no action is required. You need to take action only if you use `github_release` in a custom flow.

1 条评论
0/9000

I've had a bash at the #Advanced Mapping​ Recurring Donations Recipe. This brings in the Recurring Donations and the first Opportunity is created by the NPSP Data Import.

 

Recurring Donations Recipe

Attach a Recurring Donation to Contact1

To link a Recurring Donation to Contact1, follow the steps below.

  1. Prepare Salesforce for the Recurring Donations Object Group, and create these fields on the NPSP Data Import object:
  • Recurring Donations Imported (lookup)
    • Recurring Donations Import Status (text)
  1. Add at all the fields to map on the NPSP Data Import object. Make sure the field type matches the type on the Recurring Donations Object, such as:
  • Recurring Donations Type  (Text)
  1. In NPSP Settings, create a new Object Group for Recurring Donations 1 with the following information:
  • Group Name: Recurring Donations
    • Object Name: Recurring Donations
    • Is Child/Parent: Child
    • Of This Mapping Group: Contact 1
    • Through This Field: Contact
    • Link to Field: Recurring Donations Imported
    • Import Status: Recurring Donations Import Status
  1. Add Field Mappings for the Recurring Donations  Object Group:
  • Select Recurring Donations Type (Recurring_Donations_Type__c), and map it to Recurring Donations Type (npsp__Recurring_Donations_Type__c)
    • Repeat for all fields to be mapped.

 

Notes:

  • You will need to create another Object Group and mapping if you wish to import to Account1.
  • I would recommend setting a value and mapping for Recurring Donation Name field else it will default to the Recurring Donation ID.

 

I also have screenshots if they would be helpful.

8 条评论
0/9000

🎉Announcing the launch of Impact Lab’s FIRST open-source app, Service Match!!🎉

 

Service Match is designed for case managers who connect people experiencing homelessness to vital human services. It streamlines finding, making, and following up on service referrals, freeing up time for more meaningful interactions with clients.

 

Service Match was co-designed and developed by a passionate group of Community fellows and pro bono volunteers. It is open sourced and free to those who want to download it.

 

Check out our announcement blog to learn more about Service Match and Impact Labs. You can help us improve Service Match by sharing your thoughts and suggestions in our Trailblazer Community group

2 条评论
0/9000