You need to sign in to do that
Don't have an account?
Mike Leach
ExternalID Metadata Lost on Packaging
Has anyone else seen this?
1) Create a custom object
2) Create a custom field on object and mark it as "ExternalID"
3) Use field as primary key in upsert calls and all works fine.
4) Package and upload to AppExchange
5) ExternalID gets set to false. Upserts fail.
Perhaps AppExchange pre-processing makes the assumption that only customers can defined External IDs? That makes sense for native objects, but not custom objects designed to behave in a composite context.
Bug? Operator error in packaging? Expected behavior?
Thx!
-Mike
I've inserted an issue into our system, bug # 92862,
Subject: package an ExternalID field, then install from appexchange, field is no longer ExternalID
it may take a few days for our team to research this, please check back or call support and ask about this issue by number.
Therefore, this is not an actual bug in the package / install process, and this issue would become a feature request.
Until then,
You will have to document for your end users that they need to go into the field definition and enable the custom index / external ID after install.
Krishna
Best,
Jim
Director, Platform Product Management
Krishna