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.

relating relations....indexing issue

3rdparty
in Relationships

Featured Replies

I am trying to create a portal based on a relationship that looks at two fields in a file, one of which is generated from another existing self-relationship. However I can't, as apparently the field that already depends on the slef relationship cannot be indexed. Is there any way around this problem?

In the attached example, the relationship I want to create would look at "UniqueProjBud" and "Unique key". But UniqueProjBud is already a result of a self-relation (that returns 1 or 0 depending on the uniqueness of the record) and thus the new relationship then will not work.

Grateful for any tips

jw

testdb.fp5.zip

Hello jw,

There are a few ways to approach this.

One of them, is to use a filtered value list as the basis for the left-key for the relationship.

I've modified a copy of your file to set up your 'Unique ProjBudgSelf' relationship in this way. See attached.

testdb.zip

Create an account or sign in to comment

https://fmforums.com/topic/25766-relating-relationsindexing-issue/
Go to topic listing

Important Information

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

I accept

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.