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.

Featured Replies

I have a table where the data comes in flat...

the data columns has all the data to create 3 additional upper level hierarchical structures.

In the past I would just export a sub summarized set this data several times then import the data into

the corresponding upper levels.

I am trying to figure a way to import the data sub summarized. So that I can avoid the "temp" files that I would have to generate.

This represents my tables.

Data is imported raw into LevelD

LevelA -< LevelB -< LevelC -< LevelD

I have tried Looping scripts but it takes way too long the fastest way is importing the records.

and the fastest way to get the set I want is by sub summary export. I am hoping FP 7 can leverage

some more features that eludes me.

Thanks

FileMaker Version: Dev 7

Platform: Mac OS X Panther

  • Author

I can't believe it I figured it out...

This is how I did it....

In my Level D table I added 2 fields...

keyB [result text] a_ID & " - " & b_ID

keyC [result text] a_ID & " - " & b_ID & " - " & c_ID

Then I created 3 Value Lists.

val_A

Uses Values from "Level D" first field = "Record_ID"

also display values from second field = "a_ID"

Sort using Second field

val_B

Uses Values from "Level D" first field = "Record_ID"

also display values from second field = "keyB"

Sort using Second field

val_C

Uses Values from "Level D" first field = "Record_ID"

also display values from second field = "keyC"

Sort using Second field

Then Created 1 script. "GetRelated"

Set Field [LevelD::gLevelA; ValueListItems ( Get ( FileName ) ; "val_A" )]

Set Field [LevelD::gLevelB; ValueListItems ( Get ( FileName ) ; "val_B" )]

Set Field [LevelD::gLevelC; ValueListItems ( Get ( FileName ) ; "val_C" )]

From here I created 3 self-relationships:

gLevelA = Record_ID

gLevelB = Record_ID

gLevelC = Record_ID

The next script will first goto the related records in turn after each time I found the related set I can then bring up my target table and perform an import only importing the files I need. Then go on to the next.

The net result is that the one flat file that has Hierarchal data can be split up w/ out the need to create any sub-summarized exports or perform complex looping scripts.

If I get a chance I will create a demo file...

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.