This is not my installation, I am helping Tom Running get his setup
working so I do not have the whole picture.
On 17/01/2015 4:49 AM, Pierre Smits wrote:
Nice example, Ron,
But what do the externalId fields stand for in the <Party> records? Is
this a value defined to serve as some kind of internal identifier? Or
is the value defined by the party and assigned to you as some kind of
customer ID?
This is the "customer number"
I am not sure how they are assigned but I am pretty sure that they are
unique.
I would think that they would have a 1-1 mapping with PartyID.
The sample data that comes with OFBiz uses the customer name as an ID.
The customer number would be an alternative but I did not see any
examples where this is done nor any place to put the name.
If the latter, what do you do when you have multiple internal
organisations and each has a different identifier assigned by that
party? Where (in what entity would you capture that? And how would
such look like (visavis the OFBiz datamodel)?
Not sure what you mean here.
Do you mean that the Sales department gives it a number and the Accounts
payable department gives it another number?
I am still trying to come to grips with the data model and the wiki's
description of it and how to use it for moving data between OFBiz and
other systems..
Best regards?
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com <http://www.orrtiz.com/>
On Fri, Jan 16, 2015 at 8:42 PM, Ron Wheeler
<[email protected]
<mailto:[email protected]>> wrote:
Does this look like a file that could be imported to produce 2
customers. Both should be assigned to "LESLIE".
I gather from the partyRelationshipName that this is the correct
Type
<PartyRelationshipType description="" hasTable="N" parentTypeId=""
partyRelationshipName="Account owned by"
partyRelationshipTypeId="ACCOUNT" roleTypeIdValidFrom=""
roleTypeIdValidTo=""/>
The partyRelationshipTypeId="ACCOUNT" could be better.
partyRelationshipTypeId="ACCOUNT_OWNER" would be clearer and more
consistent with
<PartyRelationshipType description="" hasTable="N" parentTypeId=""
partyRelationshipName="Lead Owned by"
partyRelationshipTypeId="LEAD_OWNER" roleTypeIdValidFrom=""
roleTypeIdValidTo=""/>
and
<PartyRelationshipType description="" hasTable="N" parentTypeId=""
partyRelationshipName="Lead Owners/Managers"
partyRelationshipTypeId="LEAD_OWN_GRP_MEMBER"
roleTypeIdValidFrom="" roleTypeIdValidTo=""/>
They have a SIC code and an SIC description assigned to them as
attributes.
Is there are better way to handle this (Table of SIC entities and
a relation to it or does that require code changes)?
<entity-engine-xml>
<PartyGroup partyId="FOUR SEASONS HOTEL" groupName="OFBIZ COMPANY
NAME"/>
<Party partyId="FOUR SEASONS HOTEL" partyTypeId="PARTY_GROUP"
externalId="100012"/>
<PartyRole partyId="FOUR SEASONS HOTEL" roleTypeId="CUSTOMER"/>
<PartyAttribute partyId="FOUR SEASONS HOTEL" attrName="SIC"
attrValue="13"/>
<PartyAttribute partyId="FOUR SEASONS HOTEL" attrName="SIC
Description" attrValue="Miscellaneous"/>
<ContactMech contactMechId="FOUR SEASONS HOTEL_POSTAL"
contactMechTypeId="POSTAL_ADDRESS"/>
<PostalAddress contactMechId="FOUR SEASONS HOTEL_POSTAL"
toName="FOUR SEASONS HOTEL" address1="123 Main Street"
city="NewYork" countryGeoId="USA" stateProvinceGeoId="NY"
postalCode="126785"/>
<PartyContactMech partyId="FOUR SEASONS HOTEL" contactMechId="FOUR
SEASONS HOTEL-POSTAL" fromDate="2015-01-01 00:00:00.000"
allowSolicitation="Y"/>
<ContactMech contactMechId="FOUR SEASONS HOTEL_EMAIL"
contactMechTypeId="EMAIL_ADDRESS" infoString="[email protected]
<mailto:[email protected]>"/>
<PartyContactMech partyId="FOUR SEASONS HOTEL" contactMechId="FOUR
SEASONS HOTEL_EMAIL" fromDate="2015-01-01 00:00:00.000"
allowSolicitation="Y"/>
<PartyContactMechPurpose contactMechPurposeTypeId="PRIMARY_EMAIL"
partyId="FOUR SEASONS HOTEL" contactMechId="FOUR SEASONS
HOTEL_MAIL" fromDate="2015-01-01 00:00:00.000"/>
<ContactMech contactMechId="FOUR SEASONS HOTEL_PHONE"
contactMechTypeId="POSTAL_ADDRESS"/>
<TelecomNumber contactMechId="FOUR SEASONS HOTEL_PHONE"
type="PHONE" countryCode="1" areaCode="254" contactNumber="555-4534"/>
<PartyContactMech partyId="FOUR SEASONS HOTEL" contactMechId="FOUR
SEASONS HOTEL_PHONE" fromDate="2015-01-01 00:00:00.000"
allowSolicitation="Y"/>
<PartyRelationship partyIdFrom="FOUR SEASONS HOTEL"
partyIdTo="LESLIE" partyRelationshipTypeId="ACCOUNT"
roleTypeIdFrom="_NA_" roleTypeIdTo="_NA_" fromDate="2015-01-01
00:00:00.000"/>
<PartyGroup partyId="ABC ELECTRIC" groupName="OFBIZ COMPANY NAME"/>
<Party partyId="ABC ELECTRIC" partyTypeId="PARTY_GROUP"
externalId="100041"/>
<PartyRole partyId="ABC ELECTRIC" roleTypeId="CUSTOMER"/>
<PartyAttribute partyId="ABC ELECTRIC" attrName="SIC"
attrValue="02D"/>
<PartyAttribute partyId="ABC ELECTRIC" attrName="SIC Description"
attrValue="Electrical Contractor"/>
<ContactMech contactMechId="ABC ELECTRIC_POSTAL"
contactMechTypeId="POSTAL_ADDRESS"/>
<PostalAddress contactMechId="ABC ELECTRIC_POSTAL" toName="ABC
ELECTRIC" address1="123 Main Street" city="Toronto"
postalCode="N5N 5X5" countryGeoId="CANADA" stateProvinceGeoId="ON" />
<PartyContactMech partyId="ABC ELECTRIC" contactMechId="ABC
ELECTRIC-POSTAL" fromDate="2015-01-01 00:00:00.000"
allowSolicitation="Y"/>
<ContactMech contactMechId="ABC ELECTRIC_EMAIL"
contactMechTypeId="EMAIL_ADDRESS" infoString="[email protected]
<mailto:[email protected]>"/>
<PartyContactMech partyId="ABC ELECTRIC" contactMechId="ABC
ELECTRIC_EMAIL" fromDate="2015-01-01 00:00:00.000"
allowSolicitation="Y"/>
<PartyContactMechPurpose contactMechPurposeTypeId="PRIMARY_EMAIL"
partyId="ABC ELECTRIC" contactMechId="ABC ELECTRIC_MAIL"
fromDate="2015-01-01 00:00:00.000"/>
<ContactMech contactMechId="ABC ELECTRIC_PHONE"
contactMechTypeId="POSTAL_ADDRESS"/>
<TelecomNumber contactMechId="ABC ELECTRIC_PHONE" type="PHONE"
countryCode="1" areaCode="506" contactNumber="555-4433"/>
<PartyContactMech partyId="ABC ELECTRIC" contactMechId="ABC
ELECTRIC_PHONE" fromDate="2015-01-01 00:00:00.000"
allowSolicitation="Y"/>
<PartyRelationship partyIdFrom="ABC ELECTRIC" partyIdTo="LESLIE"
partyRelationshipTypeId="ACCOUNT" roleTypeIdFrom="_NA_"
roleTypeIdTo="_NA_" fromDate="2015-01-01 00:00:00.000"/>
</entity-engine-xml>
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
