Problem/Motivation

Right now we can't actually be certain that users won't create unexpected relationships. If we plan to do stuff like automation in the future we may want to add error checking to our core crm_contact relationships so we don't get confusing bugs because a power user got creative.

Steps to reproduce

- I create a Person contact with the given name "TestPerson1"
- I create a second Person contact with the given name "TestPerson2"
- I go to the Add Employment ~/crm/relationship/add/employee
- I type "TestPerson1" into the Employee field to get it to do a lookup, then copy that lookup and put it into the Organization field (AKA "TestPerson1 (crm_contact id)")
- I type "TestPerson2 into the Employee field to get it to do a new lookup
- I submit the form
- I see that I've successfully created an Employment relationship between 2 Person contacts

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork crm-3543672

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

speckles created an issue. See original summary.

bluegeek9 made their first commit to this issue’s fork.

bluegeek9 opened merge request !103

  • bluegeek9 committed 449ea38d on 1.0.x 
    [#3543672] feat: There's no error checking on the type of crm_contact...
bluegeek9’s picture

bluegeek9 commented
Status: Active » Fixed
//www.flaticon.com/free-icons/thank-you Thank you for your contribution! Your continued support makes this project sustainable.
There are multiple ways to show appreciation for the work contributed to this project including:
  • Triage issues and adding more context to existing issues.
  • Flagging CRM as a favorite on the project page to help others discover it and show your support.
  • Review the Developer Docs for accuracy and clarity.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.