Bulk Object Field Creator
BOFC (Bulk Object Field Creator) is a 100% native Force.com app built to simplify bulk Salesforce metadata operations. It helps Admins and Developers easily manage, compare, and move metadata with just a few clicks. It saves time, reduces mistakes, and boosts productivity by supporting tasks like cloning, exporting, updating, and comparing across one or multiple Salesforce orgs. Major Features: ⚡ Perform bulk Create, Update, Delete (CRUD) operations on Objects and Fields 🔄 Clone metadata like Flows, Profiles, Picklists, Permission Sets, and Reports across the same or external orgs 📊 Compare & Export multiple Profiles, Permission Sets, and Process Builders 📂 Export Objects, Fields, Validations, Record Types, Page Layouts, and Rules (Assignment, Validation, Workflow) ✅ Export & Update Field Permissions at scale 🛠 Import, Update, Delete, and Export Validation Rules 🎯 Bulk update Picklist values for multiple Record Types 🧩 Manage Process Builders, Permission Set Assignments, Flows, Apex & Visualforce Code (using Code Comparator) NOTE: - 24×7 dedicated support with quick response times. - 100% Native Salesforce App—does not transfer data or send emails from Salesforce
Top keywords
- bulk4×2.40%
- export4×2.40%
- salesforce4×2.40%
- update4×2.40%
- metadata3×1.80%
- multiple3×1.80%
- permission3×1.80%
- 1002×1.20%
- 100 native2×1.20%
- builders2×1.20%
- code2×1.20%
- compare2×1.20%
LTI-Bug Trapper
VF, Apex, Lightning tools used by Salesforce are great, but one thing missing from each of them is a common way of handling errors. When working with development language and tools outside of a platform, you can pretty much whip up an existing solution to handle errors in minutes. When it comes to Salesforce, there are a lot of creative ways, but it’s a little different when it comes to the tools we mentioned above. The inability to query Salesforce Data directly from the controller causes challenges, as it becomes a little bit more difficult to log errors. You can catch handled or unhandled exceptions (if Locker Service is disabled), but you are still responsible for sending that to an Apex Controller to save that to your custom object. Now there are plenty of error logging solutions out there, Sentry, Bugsnag, Airbrake, but none of these have direct support for Salesforce. These solutions come with some great features that can save time when rolling your own solution with a custom object. The current solution makes it easier for Salesforce developers to log to a central solution
Top keywords
- salesforce5×2.67%
- errors3×1.60%
- there3×1.60%
- apex2×1.07%
- comes2×1.07%
- controller2×1.07%
- custom2×1.07%
- custom object2×1.07%
- little