Posted by
cjhowe on
URL: http://ofbiz.116.s1.nabble.com/Dev-Party-to-Geo-assoc-entity-tp166878p166881.html
What limitations are you finding using the current
data model to group people this way? ie a territory
is a geoId that consists of zip codes, city,
etc...anyone who has a zip code or city etc as their
primary address belongs to that geoId. Seems to break
normalization unless something is limited by the
current structure.
--- Si Chen <
[hidden email]> wrote:
> customers in a territority.
>
> Chris Howe wrote:
>
> >What functionality are you thinking of?
> >
> >--- Si Chen <
[hidden email]>
> wrote:
> >
> >
> >
> >>Hi everybody -
> >>
> >>I'm thinking about adding an entity which would
> >>associate Parties with
> >>Geos, such that a particular party would be
> >>associated, with say,
> >>Florida or Europe. I doesn't seem like there is
> >>anything like that
> >>right now. How does PartyGeoAssoc with partyId*,
> >>geoId*, fromDate*,
> >>thruDate sound?
> >>
> >>Si
> >>
> >>_______________________________________________
> >>Dev mailing list
> >>
[hidden email]
> >>
http://lists.ofbiz.org/mailman/listinfo/dev> >>
> >>
> >>
> >
> >
> >_______________________________________________
> >Dev mailing list
> >
[hidden email]
> >
http://lists.ofbiz.org/mailman/listinfo/dev> >
> >
> >
>
> _______________________________________________
> Dev mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/dev>
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev