Most likely one of your read-only fields has invalid logic. If it’s obvious which field is problematic, you can post its contents here and we can assist. If it’s not clear, I would approve and publish the fields one-by-one; that way you can find out which one is causing the above issue. This led me to the answer. A few custom referenced enumerations that were created to support related persistent fields had not yet been published, however, the ACP properly brought in those custom enumerations. After walking through the referenced enumerations and publishing those, the custom fields imported in the ACP package were able to publish. Thank you, Paul!
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.