Hi Jacques:
Thanks for taking the time to explain. Since I came in on the tail end
of this, I apologize if this was explained before - but I didn't
understand from the discussion you referenced.
Given what you said below:
"But if you need more than 1 id to associate 2 parties with the same
roles, as Ron mentioned in this comment, then PartyRelationship is
not enough. "
Could I be so bold as to ask: When would it ever be logical to have
multiple relationships between 2 parties with the same roles? That is,
when would it ever be a good practice not to use the PartyRelationship
Entity to begin to describe a relationship between 2 parties. I can't
think of a business case where that makes sense. The only way this would
make sense to me is if you wanted to get away from the notion of a
relational data model.
Anyhow, I'm not trying to be difficult, just trying to understand the
requirement.
Thanks so much for your reply.
Best Regards,
Ruth
On 1/14/15 3:45 PM, Jacques Le Roux wrote:
Hi Ruth,
I mean the PK is
<prim-key field="partyIdFrom"/>
<prim-key field="partyIdTo"/>
<prim-key field="roleTypeIdFrom"/>
<prim-key field="roleTypeIdTo"/>
<prim-key field="fromDate"/>
So you can have only 1 relationship between 2 parties with the same
roles, which is logical and wanted.
But if you need more than 1 id to associate 2 parties with the same
roles, as Ron mentioned in this comment, then PartyRelationship is not
enough.
This is the conclusion we got from our discussion inside OFBIZ-3764.
Jacques
Le 14/01/2015 20:07, Ruth Hoffman a écrit :
Hi Jacques:
Just curious, what do you mean by: "it's not multi valued"? I
couldn't figure out from your reference.
Thanks in advance for the clarification.
Ruth
On 1/14/15 12:58 PM, Jacques Le Roux wrote:
I agree with all that PartyRelationship is the way.
Note though that there is a limitation with PartyRelationship: it's
not multi valued.
I assume this is not problem in almost all cases but I say that
because of your question at
https://issues.apache.org/jira/browse/OFBIZ-3764?focusedCommentId=14274901
Jacques
Le 14/01/2015 17:08, Ron Wheeler a écrit :
Does anyone have any ideas about what would be the best way to
"assign" a salesperson to a customer Party?
The simplistic way is to make the name an attribute of the customer
Party.
Is there are better intermediate entity?
Ron
On 12/01/2015 11:15 AM, Ron Wheeler wrote:
I am just putting together an example of how to use ADTransform to
prepare product data to go into OFBiz.
If you would could send me some sample data in Excell, I would
prepare the ADTransform configuration to create the XML import
file required to load Party data.
You could then use ADTransform to prepare the real data for import.
Ron
On 12/01/2015 3:34 AM, Jacques Le Roux wrote:
Nothing specific, but here are few ways:
https://cwiki.apache.org/confluence/display/OFBIZ/Handling+of+External+data
https://cwiki.apache.org/confluence/display/OFBIZ/Import+Data+Using+Apache+POI+api
https://cwiki.apache.org/confluence/display/OFBENDUSER/OFBiz%27s+Data+File+Tools
Jacques
Le 12/01/2015 05:17, Tom Running a écrit :
Mass Account Data Import:
I am trying out version 13.7.01
Under SFA Manager, Accounts User Interface.
I have lot of account records from an excel spreadsheet that I want
to import to the Accounts table (not sure if it call account
table or
something else).
These are the fields within the Accounts UI that I want to import.
PARTY ID
EMAIL ADDRESS
PHONE NUMBER
CITY
COUNTRY
ASSIGN TO
Would you provide some guidance on how to accomplish this.
Perhaps, what table is handling the Accounts information?
How to go about import the data?
Is there an import template (batch job) available some where?
Thank you.
Tom
