Apex Code Development You need to sign in to do that
Don't have an account?
SteveBower We have a Problem with an Installed Managed Package... Any suggestions?
Hello, we have a managed package that has been installed into about 40 customer Salesforce accounts.
One of the fields in a custom object has been set up with the Unique constraint. This was a mistake and we find that we need to remove that constraint.
As near as we can see, if you go back to the DE account where the package was created, you are not allowed to change that option. And, there is no way to change that option in the customer accounts where the package has been installed.
Is there any way around this?
Clearly we could change our code to do something different, however that too would require changes to the Managed Package.
Clearly we could create a new DE, and a new Managed Package done *without* that constraint, but a) that's a pain, and b) it doesn't help our current customers.
I'm looking for something other than the obvious ones above. Backdoors, etc. I've filed a support question with this as well.
Thanks, Steve. sforce@stevebower.com
p.s. One thought was for future customers to create a package with the custom object with just the one field set up as non-unique. If a user installs that, and then installs the current package on top of it, that would give us what we want, but I don't know if the conflict resolution done when installing a new package is granular enough to allow the rest of the install to proceed even if that one particular field can't be installed. ?
One of the fields in a custom object has been set up with the Unique constraint. This was a mistake and we find that we need to remove that constraint.
As near as we can see, if you go back to the DE account where the package was created, you are not allowed to change that option. And, there is no way to change that option in the customer accounts where the package has been installed.
Is there any way around this?
Clearly we could change our code to do something different, however that too would require changes to the Managed Package.
Clearly we could create a new DE, and a new Managed Package done *without* that constraint, but a) that's a pain, and b) it doesn't help our current customers.
I'm looking for something other than the obvious ones above. Backdoors, etc. I've filed a support question with this as well.
Thanks, Steve. sforce@stevebower.com
p.s. One thought was for future customers to create a package with the custom object with just the one field set up as non-unique. If a user installs that, and then installs the current package on top of it, that would give us what we want, but I don't know if the conflict resolution done when installing a new package is granular enough to allow the rest of the install to proceed even if that one particular field can't be installed. ?
Thx, -S