SalesforceFoundation/Batch-Entry-for-Salesforce.com — pull request #28 by greenstork (2012-04-02 21:46:06+00:00)
Title: a minor enhancement for Batch Data Entry?

Hi Kevin,

I created a forked gitHub repository of the Batch Data Entry package, so I could make a simple change to it to work well with our GWBase template and how it handles opps. The change was to prevent the packages current default auto naming of opps, if the opp name is left blank. This allows our current opp trigger that handles naming (via a custom setting format) to work.

Specifically, I had to make three changes:
1. Created a new Custom Setting, Allow Blank Opportunity Names. Defaults to false.
2. Modified two lines of code in CTRL_BatchEntry.cls to look at this setting before doing the current autonaming.
3. Added a little code after a save in CTRL_BatchEntry.cls to requery the sobject so it displays the autogenerated name when it shows up in the list of saved records. This has the side affect of correctly showing any updated field value that trigger code may have changed, which seems like a good thing.

We’d love it if you would consider putting these changes into the offical managed Batch Data Entry package, so our clients can use the official release, and benefit from any future enhancements.

Here’s the link to the public repository: https://github.com/Groundwire/Batch-Entry-for-Salesforce.com

Let me know if you want more details or need more info.

Thanks,
Dave