Feature Requests Incident #17846

 


Summary
Project
INCDT - xTuple ERP
Incident Category
Features
Incident Number
17846
Visibility
public


Product Version
None
Fixed In Version
None


Summary
make parent-child relationship in CRM mean something (FM2)


Description

It would be really nice if the Parent CRM Account inherited certain things from CRM accts defined as children. For example, in our current dogfood database, all of us are (properly) defined as CRM accounts ourselves (as well as Users, Employees, Vendors, etc.) ... But the application has no understanding that Contact "Ned Lilly", which is associated with CRM Account NED, should also be associated with CRM Account XTUPLE by inheritance. That one relationship would be a good place to start. In the future, it would be nice to see other things like Characteristics, Comments, History, etc., flow up the inheritance tree too (as they do with the CRMAcct/Customer relationship, for example).

As a minor tangible example of this, when I entered this issue, and put it under CRM Account XTUPLE, I wasn't able to select my Contact as the person reporting the issue (at least without going into the search contact widget, unchecking "search only XTUPLE", etc.)


Details
Reporter
ned
CRM Account
xTuple
Status
Resolved
Assigned
reddog


Priority
Very High
Severity
Normal
Updated
08-31-15 14:35
Resolution
Open



Comments

DateUsernameComment
08/31/15 14:35reddog

as suggested by the submitter, this change represents a "good place to start" and does not fully implement the CRM Account parent/child paradigm. additional improvements should be submitted as separate feature requests.

change widgets comments, contactWidget and metasql contacts-detail to include child CRM Accounts when listing comments and contacts of the parent CRM Account

06/14/12 12:05ned

It would be really nice if the Parent CRM Account inherited certain things from CRM accts defined as children. For example, in our current dogfood database, all of us are (properly) defined as CRM accounts ourselves (as well as Users, Employees, Vendors, etc.) ... But the application has no understanding that Contact "Ned Lilly", which is associated with CRM Account NED, should also be associated with CRM Account XTUPLE by inheritance. That one relationship would be a good place to start. In the future, it would be nice to see other things like Characteristics, Comments, History, etc., flow up the inheritance tree too (as they do with the CRMAcct/Customer relationship, for example).

As a minor tangible example of this, when I entered this issue, and put it under CRM Account XTUPLE, I wasn't able to select my Contact as the person reporting the issue (at least without going into the search contact widget, unchecking "search only XTUPLE", etc.)



Files

No Files

Related Documents

TypeNumberDescriptionRelationshipRemove
ProjectXTUPLEAPPSPorted From Mantisx


Subscribers

You do not have permission to view subscribers.


Incident History

DateUsernameFieldChange
06/14/12 12:05nedNewIncident Added
06/14/12 14:42ptylerStatusStatus Changed: New -> Confirmed
07/01/13 15:32jrogelstadCharacteristic Kickstart Added: "True"
07/01/13 15:32jrogelstadCharacteristic Time Estimate Added: "4"
11/18/13 14:57jrogelstadPriorityPriority Changed: -> Very High
01/12/15 17:32missyDescription Updated: "make parent-child relationship in CRM mean something" -> "make parent-child relationship in CRM mean something (FM2)"
07/02/15 15:00gmoskowitzSeveritySeverity Changed: -> Normal
08/31/15 14:30reddogCharacteristic CodeReview Added: "Needed"
08/31/15 14:30reddogStatusStatus Changed: Confirmed -> Resolved
08/31/15 14:30reddogAssignedAssigned to: "" -> "reddog"
08/31/15 14:30reddogResolutionResolution Changed: -> Open
08/31/15 14:30reddogCharacteristic Doc Flag Added: "True"