0

We have a managed package currently using custom settings, and it has been installed in all editions except Database.com, i.e. Group, Professional, Performance, Unlimited and of course Developer.

We are interested in using custom metadata types to store some application configuration details, but according to this, custom metadata types are not available in Group edition.

Therefore, if I package custom metadata types with the managed package, will it prevent Group edition owners from upgrading or installing the package?

Also, I just created an Partner Group edition, and I can actually see the Custom Metadata Types menu in the setup? Could it be that the documentation is out of date?

Improve this question
1
  • When the metadata your are updating or installing via managed package it will throw run time error if it is not supported in that org. Also it should be available in all types of edition where we can write apex but I am not sure on that.
    – Rishi Golyan
    Jul 5, 2017 at 8:14

1 Answer 1

Reset to default
2

The doc is inaccurate; I'll let our writer know. Group Edition is like Professional Edition with respect to custom metadata types; they can't create their own but can install them from Aloha-certified managed packages.

Improve this answer
0

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .