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.

Portal not "refreshing"

Featured Replies

I have looked for an answer to this problem but can't seem to find it.

I have 2 dbs - Clients and Episodes (a given client can have more than one episode of contact). In the Client file, I have 2 portals - one is a brief summary of each episode, the second is a single line portal containing a number of fields giving more complete information about the episode chosen from the first portal. This portal is invisible unless triggered by a specific value in the episode file.

If I browse a client record in the Clients db, choose an episode from the first portal and display the complete details in the second portal, then browse other clients in the Clients db, the contents from the previous selection stay in the second portal in each browsed record until another episode is chosen in the first portal.

Is there a way to cause the portal to only display data from the record being browsed, and for this to update as different records are browsed? My only solution so far is to use navigation buttons to go from record to record, with the inclusion of a script with that button that chooses the first line of the first portal on entry to that record.

Any help will be greatly appreciated. By the way there are no calc fields in the portals.

Cheers, Murray

Hi Murray,

If you don't want to script the value of this global field(which I assume it is) through Navigation button, you could do it through a calculation that will update from record to record.

You could have your script (in portal) set the value of the global field with the related ID (what you're currently doing) + the value of the current record to another global (g_Record_ID)

2 relationships needed ???

StandardRel= Main::Record_ID::Related:Record_ID

FilteredRel = Main::c_ConditionalKey::Related:RelatedRecord_ID

Change your "toggle" script to :

SetField[g_Key,::Relationship::RelatedRecord_ID]

SetField[g_Record_ID,Record_ID]

ExitRecord

Then, use a calculation as your Left key for the portal that will either hold the selected RelatedRecord_ID (g_key) if not empty, or the FIRST related record from the current record browsed, coming from 'StandardRel'

c_ConditionalKey = Case(not Record_ID = g_Record_ID, ::StandardRel::RelatedRecord_ID, Case(not IsEmpty(g_Key), g_Key, ::StandarRel::RelatedRecord_ID))

Use this new 'Filtered Rel' relationship instead of your old one.

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.