Jump to content

Portal in Table not showing up!


tmas73
 Share

This topic is 5585 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I have a problem to show the Fields from the "Inventory" tabe to show up in the "Contacts" Table.

I created the "Inventory" fields in the contact table but none show, is it a relation problem?

How can I get those relations to work?

Thanks for the help

Thomas

Graph.pdf

Fields.jpg

Edited by Guest
Link to comment
Share on other sites

It is difficult to tell by your example. We will need to know the relationship keys involved. What fields relate them? Please provide field names and the data types and whether the fields are global, calculation, unstored, indexed and so on.

Have you double-clicked each field in that portal and made sure they are also based upon the Inventory table occurrence? If they are, then your relationship probably isn't working.

Link to comment
Share on other sites

1) You have no records in Sales but your relationship between Contacts and the portal goes THROUGH your Sales table.

2) Create a record in Sales for Marinello Thomas and select an Inventory Item.

3) But it STILL will not work. Why? Because you have included the BillToName in the relationship between Sales and Inventory and it should NOT be so. Inventory doesn't NEED to know the BillToName because it can pull that info from the Sales table (actually, it could pull it through Sales table to Contacts). Delete BillToName in this relationship (between Sales and Inventory) so only the ItemNumber binds them.

Poof - relationship portal fills.

An few observations ... You are using 8 repeating fields to hold Item Name, Selling Quantity and Price. This is not a good structure and I highly suggest you change it now while the design is still new. Also, you are basing your relationships on names - very very bad. Use unique ID serials to hold your relationships together. I see you use StampID so you must understand how key fields work.

These two errors in your design will haunt you and cause nothing but problems. Again ... ditch them both and set your relationships properly. :wink2:

LaRetta

Link to comment
Share on other sites

The issue is this: You have the theory of using IDs REVERSED. Contacts needs to have a ContactID - remove all those other IDs from Contacts. Each table should have it's OWN primary ID. ONE Contact can have MANY Projects. One Project can have many Sales.

Memorize this principle: To create a relationship between a ONE to a MANY, you put the ONE-side ID (ContactID) in the MANY-side table (Sales or Projects). When you do this, the ContactID is called the foreign key because it resides in another table (as well as being the Primary key in Contacts). Then join THAT ContactID back to the ONE-side table ID. See FM Help 'Working with the Relationships Graph.'

I have no idea how your structure should be - only you know that. You've changed your file completely. And you still are using repeating fields. I can't help you with your structure until YOU understand what you need. Here is a sample file showing how a basic relationship (one-to-many) would work. Again, I highly suggest you ditch the repeating fields here as well.

I hope the file is helpful. :wink2:

Relationship.zip

Link to comment
Share on other sites

This topic is 5585 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.