The document outlines best practices for developing products for Salesforce's AppExchange, emphasizing the importance of creating upgradeable applications. It discusses the benefits of avoiding Salesforce standard pages, pick-list types, and reports within managed packages to ensure smooth upgrades. The conclusion stresses the necessity of being 'upgradeable' and recommends consulting the ISV guide during product development.

1. AppExchange
Practices I discovered during AppExchange product development
Japan Dreamin’ 2020 (2020/01/25)
TeamSpirit Inc.
@a_kuratani

2.
What to talk or not to talk about today
What to talk
AppExchange
Important things in AppExchange development
Practices for developing a growing product
What not to talk
Best Practices
How to make products that sell a lot
#

3. Akira Kuratani /
@a_kuratani
kuratani
TeamSpirit Inc.
Engineering Team / Director
Podcast(migration.fm)
me

7. AppExchange
Important things in AppExchange Development

8. Upgradeable

9. Upgradeable
Why?
AppExchange
If you provide the AppExchange application to a large number of users and continuously add
features, we need to minimize the upgrade effort so that users can use the new version.

10. Growing products

11.
Generic Strategy
Upgradeable

12. Which development style is better?

13. Declarative development
or
Code development

14. or
Declarative development or Code development

15. or
Declarative development or Code development

16. Which development style is better?
Code development if provided continuously

17.
What is upgradeable?
•
Which components of the managed package can be upgraded.

18.
What is upgradeable?
•
Which components of the managed package can be upgraded.
ISV
Peruse ISV Guide

19. Practices for developing a growing product

20. Salesforce

21. Salesforce
Should we use the Salesforce standard pages?
•
Once the object is defined, the list page and detail page can be used immediately.
•
We can switch page layout by record type.

22. My Answer
Salesforce
Salesforce standard pages should not be used as much as possible.

23. My Answer
Salesforce
Salesforce standard pages should not be used as much as possible.
Why?
Page layout is not upgradeable.
✕

24. My Answer
Salesforce
Salesforce standard pages should not be used as much as possible.
How to do?
Visualforce
Use upgradeable components such as Visualforce pages.

25.
How to implement pick-lists?

26.
How to implement pick-lists?
•
Use picklist type
•
Easy implementation
•
Validation by item value

27. My Answer
Don't use pick-list type.

28. My Answer
Don't use pick-list type.
Why?
Cannot add / change / delete pick-list type item value of target organization when
upgrading.
✕

29. My Answer
Don't use pick-list type.
How to do?
1.
Holds data in text type. Item values are managed separately.
2.
Use custom metadata type pick-lists.
3.
Master manage.

30. My Answer
Don't use pick-list type.
How to do?

31.
How to provide reports?

32.
How to provide reports?
•
Providing reports in managed packages
•
Easy implementation

33. My Answer
Don’t include reports in managed packages.

34. My Answer
Don’t include reports in managed packages.
Why?
Reports cannot be upgraded.
✕

35. My Answer
Don’t include reports in managed packages.
How to do?
•
Provide only report type, not report
•
Isolate managed packages that provide reports.

36. Conclusion

37. Conclusion
• AppExchange
It is important to be “upgradeable” in AppExchange development.
• ISV
Peruse the ISV guide while imagining operations.

38. Thank you
Practices I discovered during AppExchange product development