I'm trying to erase 2 custom objects from my sandbox but for some reason the option is greyed out. I've erased a one-to-many object before but it seems that this many-to-many setup does not want to leave.
Per the docs: "If the custom object is linked to an intermediary object, you must delete the intermediary object first." I'm trying to erase the intermediary object but unable to do so. I've erased all the fields on it that I could too but still nothing but a greyed out delete option.
Just FYI...I received a notification yesterday that the patch was released for our instance. I tried deleting the CO in our sandbox and it work Ok this time.
Thanks, -Markus
Can confirm, able to erase many-to-many config as well.
Thanks for the update. Going to check our instance now.
Thx for letting us know
It has been escalated to engineering, there are multiple tickets for this issue. Still waiting for a solution.
Thanks everyone, good to know it's not just me. I have an open ticket so I will let you all know the outcome.
Hi Tony,
Have you heard back from support in regards to your ticket? I also opened a ticket on Tuesday, but have not heard back yet; any info is appreciated. Thanks, -Markus
Same boat Markus, rep said she will update me on the progress later today. Sounds like it will not be a quick fix but hopefully I will get some more detail later and update everyone.
-Tony
I just encountered this issue today as well. It has never been an issue in the past for us
Hi Tony,
We are having the same problem, please let us know what was the outcome on your end...
Thanks, -Markus
Can you add a screenshot of where you're trying to delete the intermediary object? Or copy any error text you're getting?
No errors, just do not have the option.
In right column list:
Hi Tony,
Have you tried to remove one or the 2 link fields before trying to erase the object?
-Greg
I have, but when I go to field actions, no dropdown actions show for linked fields. For unlinked fields I can see delete just fine.
Hi Tony,
I observe the same thing on my own instance. Weird...
It seems to be that it will take support help
I would not be surprised if it was linked to licensing issues...
Keep us posted of what support says.
-Greg