Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 396
  • Last Modified:

Portal based on relationship

Hi All,

I'm working with a portal and am having trouble getting the right information in it.  

I have contacts that I'm keeping track of along with their spouse and children.  In the Contacts table, there is a ContactID assigned to each record along with an auth_ContactID.  The contactID is unique to all records, but the auth_ContactID will reflect the head of the family (HEAD) and so all family members (DEPENDANTS) will have the same auth_ContactID (the HEAD will have the same number for both their ContactID and auth_ContactID).

I've tried creating the portal  based on a table occurance Contacts_Related that is based on the Contacts table with the relationship:

Contacts::ContactID = Contacts_Related::auth_ContactID. (The portal won't popluate)

The portal is on a layout based on the Contact table and ideally, I would like it to populate with all the DEPENDANTS of the HEAD contacts.

This isn't working.  The only way that I can get the portal to populate at all is by making the relationship based on:

Contacts::auth_ContactID = Contacts_Related::ContactID (The portal populates with the HEADS's data in the DEPENDENTS's Contact record, but not the other way around)

Contacts::ContactID = Contacts_Related::ContactID (the portal populates with the Contacts own record and no one
else's)

HELP!! Thanks:)
0
c1peoples
Asked:
c1peoples
  • 3
1 Solution
 
lesouefCommented:
see this if it fits:
http://www.lesouef.net/files/heads_dependants.fp7
for each member head, it show all members.
0
 
lesouefCommented:
simply browsing would show members for all members, not for heads members only; this is why I use a global field to only see heads in the popup head selection.
note that using a table for heads and another for members is another easy solution.
0
 
c1peoplesAuthor Commented:
Do you think that my problem was that the my layout was based on the HEAD (one side of the relationship) instead of the DEPENDANT (many side of the relationship) and the portal on the DEPENDANT instead of the HEAD?  I seem to have done the opposite of what you did.

Thanks!!
0
 
lesouefCommented:
the relation is not the problem, but you really have to know what you do when choosing which end of the relationship you gonna use as the layout table, the other one being used for the portal. In yr case the "one" end is to be used for the layout, and the "many" end for the portal
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now