Closed GoogleCodeExporter closed 9 years ago
Is the role not being updated causing an issue? Or is the issue that the ID for
the role is not being updated?
That field should only be referenced during the initial creation of the
opportunity, after that, it shouldn't be relied on for accurate information.
(Since you can theoretically change the Opportunity Contact Role to a different
Contact, and it wouldn't be updated to reflect that).
Either way, I'll put the bugfix in the next C&O release, just curious about the
use-case.
Original comment by kbro...@gmail.com
on 2 Sep 2011 at 10:06
I did not have a specific use case but I noticed it was not updated after a
merge and thought I would post it as a bug in case someone did use that in some
manner then it would be incorrect.
Original comment by dwhi...@gmail.com
on 3 Sep 2011 at 2:12
It is the NPSP custom Contact ID Role field on the Opportunity object that is
not being updated. The contact role is updated correctly.
Original comment by dwhi...@gmail.com
on 3 Sep 2011 at 2:14
Understood - I can patch it for the next release, should be in the early fall.
Thanks for submitting!
Original comment by kbro...@gmail.com
on 3 Sep 2011 at 2:40
Just dug through the code on this, its not something we're going to be able to
support. The Contact Merge functionality uses SFDC Apex Merge command, that
automates the reparenting of children records, including Opportunities. That's
a good thing, as we don't need to issue updates for each type of record (Opps,
Tasks, etc.) OTOH, it also means we can't control the reparents, and since the
ID for Role field is a standard text field and not a Contact lookup, there's no
way to indicate it needs update without a major rearchitecting.
I'm going to close the issue as WontFix - Thank you for submitting though!
Original comment by kbro...@gmail.com
on 22 Sep 2011 at 7:10
Original issue reported on code.google.com by
dwhi...@gmail.com
on 2 Sep 2011 at 12:07