What we are trying to accomplish is for the "Order" to be seen in both customer records via a portal.
this may be where a second "occurrence" of the Customer tables is placed on the graph. You can name it "Customer_endUser"
then have a second field 'id_enduser' in Orders
so your graph is something like:
Customer::ID_customer = Orders::id_customer
Orders::id_enduser = Customer_endUser::ID_customer
You are choosing the id from customer, but placing inside the Orders into two fields. So to get the other field data, the relationship is needed (once for contractor and once for enduser).
Yes, there are other ways without relationship, but this is a basic way that may make sense to you.
(If you are familiar with SQL, the same table used twice in a query would have an alias to make them pull different information - this is similar to the relationships above)
if you have the relationships as I defined, then there would be two portals on the Customer layout. One where the customer is a contractor and one where the customer is an enduser. Is this what you can use? or perhaps you had something else in mind?
Not exactly. In our current "Customers" table a customer can be labeled; (end user), (contractor), (engineer), etc.
An "Order" can be generated by a "Customer: no matter what type that "Customer" is labeled; (end user), (contractor), (engineer), etc. And that "Order" can be seen in the "Customer" record via a portal.
When an "Order" is placed by a (contractor or engineer) "Customer" we would also like to relate that "Order" to an (end user) "Customer". Can a second portal be added to the "Customer" record showing the information from the "Order" place by a (contractor or engineer)?
If I'm understanding correctly, you can absolutely create a second relationship, with the caveat that you would need two separate portals on the customer screen, one for orders a customer is contracted to, and another for orders a customer is the end user.
If you want to get around the two portal problem, you can either show and hide the two portals based on the customer type (contractor, end user)
OR you could make a multi-key relationship, where the customer foreign key in order (id_customer) has both customer IDs listed in a return-delimited list within the key. This would successfully resolve both relationships to both customer records.
This technique is demonstrated in the FileMaker knowledge base here: About match fields for relationships
I think I got it based on what you supplied earlier, thank you