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.

Changing data in a portal by script

Featured Replies

I'm working on a receiving db where I'm getting the raw info from an old DOS accounting system (so I can't set everything up right the first time!). I'm currently importing two files into two dbs. I have a header file (PO #, date, name of vendor, etc.) and a line items file.

The line items come to me flagged by a status field as either Open or Complete. Typically, a 100 line PO could dribble in from the vendor over several months, meaning any given line item could go from Open to Complete without affecting the status of its neighboring line items.

I've set up a layout in the header db with a portal that shows all line items associated with a PO#. What I'd like to do is make a button that runs a find script somehow that will allow only the Open items to display in this portal. I tried putting the status field in the portal and doing a find on it manually for "Open". It found them all, but the portal still displays all line items. Apparently the portal ignores what is being found or not found in its related db.

A work-around I thought of is to do a daily find and export of all Open items into a third db, then duplicate my portal layout, except the new portal is related to the third db. That way, my user button to show all line items would go to layout A, and the one to to show only Open items would lead to layout B.

But the daily dump seems clumsy and a pain. Is there a better way?

Steve Brown

I'd recommend creating a separate relationship, that will show only related Open Line Items. you can do this by creating a multi-key. For example, if the status of a Line Item is either Open or Closed, then create a field in Line Items like this:

(PO_ID]) & (LineItemStatus)

and then in the PO table, create a field that concatenates its PO# with the word 'Open', like this:

(PO_ID) & "Open"

then, from the PO, establish a relationship between these two fields. In a portal for that new relationship, it will show only Line Items from that PO, that are Open.

You could add another relationship for 'Closed' related Line Items, and then place the two portals side by side, with a script that can mark any given Open Line Item as Closed, thereby moving it from the Open portal to the Closed portal.

  • Author

It works like it oughta. Thanks.

Steve Brown

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

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.