2

I have enabled person accounts in my org and have a requirement of creating a managed package. This package concentrates on person accounts and several other custom objects. I found that we cannot reference person accounts fields directly if we are going to create a managed package as users will not have enabled person accounts in their org.

I would like to know the best practices to be followed when using person accounts with managed package with respect to coding and configuration and also any limitation that might arise later due to the use of person accounts in managed package.

Thanks in advance

  • My colleague wrote this article Invoke Contact triggers logic on Person Accounts that discusses one problem area. – Keith C Oct 8 '14 at 8:21
  • Are you using the Non Profit Starter Pack? I think it probably serves as a best practice example for how to handle person accounts using it's relationships model. Check out their code on Github. – crmprogdev Oct 8 '14 at 12:03
  • I am using a partner developer edition – Saranya Oct 10 '14 at 8:22
-1

No worries from Winter15 onwards you can package PA. Winter15 Release Notes

| improve this answer | |
  • I dont think this is the answer. It looks like comment. – AtulRajguru9 Oct 8 '14 at 9:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.