Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Related records and portals.....arghhhhhh!!!

Featured Replies

Hi there!

I

Two options:

1. Create a direct relationship using PaperID# from DB1 to DB4. Likely not practical in your particular situation. So, try...

2. Create unstored calculated fields in DB3 that reference the fields in DB4. Then display these in the portal in DB1.

or use Filtering portal using :

- A global field

- A value list of all Paper_Ids related to Customer_Id using a relationship WorkOrder:Cust_Id::Line Item:Cust_Id.

Attach this value list to the global field and set a new relationship from WorkOrder to Papers using WorkOrder:globalfield::Paper::Paper_Id.

Then use a portal with this new relationship.

Hi Peter

My reading of your post is that you assign a paper type to each line item: if this is the case create paper details fields in the line items file and use a lookup to fill them, using the relationship to the Papers.fp5 file. Once you' ve the data in the line items file you can display them in the portal

With Pupiweb's last answer, I just figured out what you were trying to achieve : You want a list of all papers related to the Customer.

There are therefore several solutions depending on your structure.

1. If the Paper_Id is related to only one customer, the simple way would be to have the Customer_Id along with the Paper_Id in the Paper.fp5 file.

2. If the Paper_Id can be related to many customers, but one Customer can only be "attached" once to the Paper_Id, you could use Pupiweb's solution working on the ine item.

3. If there is a many to many relationship, then you could :

- stil use the Line items but this portal will show duplicate entries in it.

- store the Paper_Id in a Multi-key field in the Customer file.

and last (for me...) but more complicated :

create a concanated field in Line Items = Paper_Id & Customer_id.

create a selfjoin using this concanate calc

use a case calc Case(Record_Id = Max(selfjoinon::Record_Id); Paper_Id; " " )

Index this calc in a new "text or number" field using the Modification key.

Sort your relationship to the Line item by this new indexed text/num field.

The portal won't show duplicate anymore.

Create an account or sign in to comment

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.