Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

(4) Share

Report

Posted on by Phillip U.

I have a relationship that was created between the Account and Opportunity entities due to the creation of an Account lookup field that was added to the Opp entity. The point of this lookup field is to track a third party account that is part of the sale effort but not the customer/prospect.

The problem is that when an opportunity is created from within the potential customer's account, this relationship and its mapping is auto-populating this third party account lookup field with the customer's account in addition to the potential customer field. I don't want this.

I'd like to avoid any need to write a plug-in to stop this (and I'm not sure I can even do that with a quick create form anyways). I've found out I can't delete the mapping. But can I safely delete the relationship without breaking the lookup field?

*This post is locked for comments

All responses (11)

Answers (0)

Megan House 14 on at

Like (1)

Report

Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

Does anyone know if this is still an issue or whether there is a solution to this?
waleedbinafzal 347 on at

Like (0)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

Here is 2021, the issue is still the same.

Going to use workflow for this to work for now.
meelamri 13,216 User Group Leader on at

Like (3)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

2020 :)
Piotr Gaszewski 424 on at

Like (1)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

2019 - issue still exists :D
Community Member on at

Like (1)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

It's 2017 and I have this issue too.

Is there anything out there that facilitates that?
Conor Gallagher 715 on at

Like (1)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

2 years later and still a bug! Writing a plugin or JavaScript to fix this is such a hack. For the plugin you really are just guessing if the fields were mapped with these values or if the user did actually select them. JavaScript on-load is a tad safer... but how do you know which relationship they came from?

Did you ever raise that connect bug Phillip? I'll give it a vote if you did!
Blundern 2 on at

Like (0)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

Workaround to avoid code usage:

Realtime workflow on create

Check condition

IF Opportunity:Account equals Opportunity:2ndAccountrelationship

IF True

Update and clear 2ndAccountRelationship field value

Works great.
Peter Bohn on at

Like (0)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

Hi Philipp.

You'll have my vote.

This Problem exists since years and no one cares, esspecially ms Not.

But i think...this is a no go to need to write scripts to correct bugs which are really i mean reeeaaaaallllly Bad Work from ms.

And especially if it is such easy to elaminate from ms side

just make no automatic mapping for new lookups,when a lookup to the same entity still exists and/or make a mapping manually removeable .

I am really Happy, that someone other has found the problem to.

...Band once again... IT EXISTS FOR YEARS...UNBELIEVABLE.

greets peb
Royal King 27,686 on at

Like (0)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

Javascript is executed in the tablet as well so you should be fine.
Phillip U. 2 on at

Like (1)

Report

RE: Can't disable or delete a mapping in a 1-to-N relationship - can I delete a lookup field's relationship instead?

I considered this. I've already got a nearly identical script in place on another form that has a similar lookup field issue but I'm not a big fan of doing this client side plus, it won't help tablet users as I understand it.

I guess it's time to hit Connect and suggest this be a configurable thing.