Method:CRM Customization Best Practices

1. Start With a Clear Data Model

Before building screens or workflows, define your tables, fields, and relationships. A clean data model prevents duplication, reduces complexity, and keeps your system easy to maintain.

• • Normalize your data where possible
• • Avoid storing the same value in multiple tables
• • Use custom tables for heavy customization

2. Build Reusable Screens

Instead of creating multiple versions of the same screen, build reusable components:

• • One “Edit Record” screen
• • One “Create Record” screen
• • One “List View” screen

Pass record IDs through navigation actions to keep your system clean and scalable.

3. Use Actions Instead of Code

Method’s action engine is powerful and update‑safe. Use built‑in actions whenever possible instead of custom JavaScript or HTML. This ensures your customizations remain stable across platform updates.

4. Keep Workflows Modular

Break large workflows into smaller, reusable components:

• • Validate Input
• • Create or Update Record
• • Send Email
• • Sync to QuickBooks
• • Log Activity

5. Test With Real Data

Always test with multiple users, roles, and edge‑case data. Method behaves differently depending on context, so thorough testing prevents unexpected behavior.

6. Use Permissions Properly

Don’t rely on hiding UI elements for security. Use Method’s role and table permissions to ensure sensitive data stays protected.

7. Avoid Over‑Customizing Built‑In Tables

Built‑in tables sync with QuickBooks and other systems. Add custom fields sparingly. For heavy customization, create a separate custom table.

8. Optimize for Speed

• • Reduce unnecessary actions
• • Avoid loops when possible
• • Use filtered “Retrieve List” actions
• • Load only the fields you need
• • Use pagination for large lists

9. Integrate Thoughtfully

When connecting Method to external systems:

• • Store API keys securely
• • Avoid unnecessary API calls
• • Cache results when possible
• • Log integration failures

10. Keep Your Account Clean

Schedule regular cleanup to keep your Method account fast and maintainable:

• • Delete unused screens
• • Remove abandoned tables
• • Archive old workflows
• • Consolidate duplicate fields
• • Review permissions

11. Document Everything

Every customization should include purpose, affected screens, fields used, workflows involved, and modification notes. Documentation saves hours of reverse‑engineering later.

12. Build With the Future in Mind

Ask whether your customization will scale, survive updates, and be understandable to another developer. If not, rethink the design.