SeedCodeHierarchy

Integration

SeedCodeHierarchy.Integration History

Hide minor edits - Show changes to output

February 16, 2009, at 03:04 PM by 67.160.86.122 -
Changed lines 77-78 from:
In step 5 we left a few fields that were commented out and we'll now return to fix those. Open the field definition for the field "DisplayContentsLevel1Calc" in your file and remove the leading and trailing comments (remove the /* at the beginning of the calc and the */ at the end of the calc). Now edit the field definition itself, adding the fields you'd like to see depict your level 1 record: in our example this would be "HierarchyPortalLevel1::CompanyName" (without the quotes). Note that the fields from your top level table should come from "HierarchyPortalLevel1" and that the calculation should be defined from the perspective of "Hierarchy".
to:
In step 5 we left a few fields that were commented out and we'll now return to fix those. Open the field definition for the field "DisplayContentsLevel1Calc" in your file and remove the leading and trailing comments (remove the /* at the beginning of the calc and the */ at the end of the calc). Now edit the field definition itself, adding the fields you'd like to see depict your level 1 record: in our example this would be "HierarchyPortalLevel1::CompanyName" (without the quotes). Note that the fields from your top level table should come from "HierarchyPortalLevel1" and that the calculation should be defined from the perspective of "HierarchyPortal".
Changed lines 121-122 from:
The hierarchy uses 5000 place holder records to depict the records in your tables. These record's aren't ''data'' per se, and they don't take up much room. You'll need to import these records into your file in order to get the hierarchy working, and to bring the hierarchy's interface to life.
to:
The hierarchy uses 5,001 place holder records to depict the records in your tables. These record's aren't ''data'' per se, and they don't take up much room. You'll need to import these records into your file in order to get the hierarchy working, and to bring the hierarchy's interface to life.
Changed lines 67-68 from:
Now connect Hierarchy to Hierarchy Portal, using PortalKeyCalc on the Hierarchy side, and RecordNumber on the HierarchyPortal side. Use the ">" operator so that PortalKeyCalc "is greater than" RecordNumber.
to:
Now connect Hierarchy to Hierarchy Portal, using PortalKeyGlob on the Hierarchy side, and RecordNumber on the HierarchyPortal side. Use the ">" operator so that PortalKeyGlob "is greater than" RecordNumber.
Changed line 127 from:
That's it! Your hierarchy is all set to go. Click the "show hierarchy" button to load your records  and then have fun!
to:
That's it! Your hierarchy is all set to go. Click the "show hierarchy" button to load your records  and then have fun! If you want to take advantage of the features in Example Three, you need to add a couple more things to your file and can continue your integration here: [[using example three]].
Changed lines 27-28 from:
So make a simple Table Occurrence Group (TOG) for use in the hierarchy and relate your version of Companies, Projects, and Tasks to each other as naturally as possible, even is you're using [[SelfJoins | self-joins or join tables]]. Then, rename the table occurrences so that the top-level TO (Companies, in our example) is named "HierarchyDataLevel1" (without the quotes), the next one down is "HierarchyDataLevel2", etc. You'll find a TOG like this in the relationship graph of SeedCodeHierarchy.fp7 and make sure you match the TO names used there exactly.
to:
So make a simple Table Occurrence Group (TOG) for use in the hierarchy and relate your version of Companies, Projects, and Tasks to each other as naturally as possible, even if you're using [[SelfJoins | self-joins or join tables]]. Then, rename the table occurrences so that the top-level TO (Companies, in our example) is named "HierarchyDataLevel1" (without the quotes), the next one down is "HierarchyDataLevel2", etc. You'll find a TOG like this in the relationship graph of SeedCodeHierarchy.fp7 and make sure you match the TO names used there exactly.
Changed lines 97-100 from:
Open ScriptMaker in your file and import all of the scripts from SeedCodeHierarchy.fp7 into your file. You'll see two sections of scripts within the "Hierarchy" section and you'll only need to edit the script that are in the "Data Scripts" section-- and you'll find that these edits are very simple.

-> Edit the script "Set Default Contents". This script controls the default contents of the hierarchy, controlling which records show up when you first arrive. It currently sets the variable $$Hy_Show to 15 to show the first 15 top-level records in our demo. You'll likely just want to replace "15" with "All" to show all your top-level records. The script itself contains instructions for going further and [[UsingExampleTwo | filtering]] the hierarchy by default.
to:
Open ScriptMaker in your file and import all of the scripts from SeedCodeHierarchy.fp7 into your file. You'll see a couple sections of scripts within the "Hierarchy" section and you'll only need to edit the script that are in the "Data Scripts" section-- and you'll find that these edits are very simple.

-> Edit the script "Set Default Contents". This script controls the initial contents of the hierarchy, controlling which records show up when you first arrive. It currently sets the variable $$Hy_Show to 15 to show the first 15 top-level records in our demo. You'll likely just want to replace "15" with "All" to show all your top-level records. The script itself contains instructions for going further and [[UsingExampleTwo | filtering]] the hierarchy by default.
Changed lines 105-106 from:
-> Edit the script "Go to Item". You'll see several "Go to Related Record..." steps there. Edit the step for each level to indicate the layout in your file that you'd like to use when viewing records. This is part of the routine we run when clicking on the green arrow in the hierarchy to go to an item's record in form view.
to:
-> Edit the script "Go to Item". You'll see several "Go to Related Record..." steps there. Edit the step for each level to indicate the layout in your file that you'd like to use when viewing records. This is part of the routine we run when clicking on the green arrow in the hierarchy to go to an item's record in form view. At this point, don't worry about the second half of the script that deals with multiple hierarchies.
Changed lines 115-116 from:
If you want to filter the hierarchy as we do in Example Two, you can copy the whole "begins with..." blue pill from our Example Two layout and paste that on to your layout as well. If you're interested in [[using example three]] you can move on to that after you complete the next step below.
to:
If you want to filter the hierarchy as we do in Example Two, you can copy the whole "begins with..." blue pill from our Example Two layout and paste that on to your layout as well. If you're interested in [[using example three]] you can move on to that and copy it's layout elements after you complete the next step below.
Changed lines 123-127 from:
From the Hierarchy layout in your file, select "Import Records... / File" from FileMaker's File menu and select SeedCode Hierarchy as the file to import from. Make sure the table on the left side of the import (the SeedCode Hierarchy side) is set to use the Hierarchy table, and that the import order is set to use "matching names". Then import the 5000 records, marking the "perform auto enter..." checkbox as yes.

When you created your HierarchyInterface table, FileMaker added a layout for this to your file. Navigate to that layout and select "Import Records... / File" from FileMaker's File menu and select SeedCode Hierarchy as the file to import from. Make sure the table on the left side of the import (the SeedCode Hierarchy side) is set to use the HierarchyInterface table, and that the import order is set to use "matching names". Then import the 1 interface record.

That's it! Your hierarchy is all set to go. Click the "show hierarchy" button to load your records in and then have fun!
to:
From the Hierarchy layout in your file, select "Import Records... / File" from FileMaker's File menu and select SeedCodeHierarchy.fp7 as the file to import from. Make sure the table on the left side of the import (the SeedCode Hierarchy side) is set to use the Hierarchy table, and that the import order is set to use "matching names". Then import the 5000 records, marking the "perform auto enter..." checkbox as yes.

When you created your HierarchyInterface table, FileMaker added a layout for this to your file. Navigate to that layout and select "Import Records... / File" from FileMaker's File menu and select SeedCodeHierarchy.fp7 as the file to import from. Make sure the table on the left side of the import (the SeedCode Hierarchy side) is set to use the HierarchyInterface table, and that the import order is set to use "matching names". Then import the 1 interface record.

That's it! Your hierarchy is all set to go. Click the "show hierarchy" button to load your records and then have fun!
Changed lines 101-108 from:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example two. Scroll toward the end of the script and you'll see a comment that begins "Specify the Target Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top level table. In our example this was the company name field, but you may wish to filter differently. Note that you can branch this script later to [[ Found Sets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.

-> Edit the script that begin "Sort Level...". Each script contains only one step and is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field(s) you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each level.

-> Edit the script "Go to Item". You'll see several "Go to Related Record..." steps there. Edit the step for each level to indicate the layout in your file that you'd like to use when viewing records. This is part of the routine we run when clicking on the green arrow in the hierarchy to go to an item in form view.

If your file doesn't have a script that runs on file open (Fie / File Options), you can use the "Upon Opening" script you imported from the Hierarchy. If you already have one, add a Perform Script line to your opening script to call ours at some point. You may want to delete these last two PerformScript() lines from our "Upon Opening" script if you're not showing the hierarchy right away.
to:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example Two. Scroll toward the end of the script and you'll see a comment that begins "Specify the Target Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top-level table. In our example this was the company name field, but you may wish to filter differently. Note that you can branch this script later to [[ Found Sets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.

-> Edit the scripts that begins "Sort Level...". Each script contains a "Sort" step that is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field(s) you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each script's level.

-> Edit the script "Go to Item". You'll see several "Go to Related Record..." steps there. Edit the step for each level to indicate the layout in your file that you'd like to use when viewing records. This is part of the routine we run when clicking on the green arrow in the hierarchy to go to an item's record in form view.

Lastly, if your file doesn't have a script that runs on file open (Fie / File Options), you can use the "Upon Opening" script you imported from the Hierarchy. If you already have one, add a Perform Script line to your opening script to call ours at some point. You may want to delete these last two PerformScript() lines from our "Upon Opening" script if you're not showing the hierarchy right away.
Changed lines 113-116 from:
Now that you've got all the necessary scripts in place you're ready to add the contents of the Hierarchy layout (from Example One). Select all of the layout elements from the Hierarchy layout in SeedCode Hierarchy and then move to the Hierarch layout in your file, removing the Header and Footer parts, if any. Then paste the layout elements into your layout. Don't worry if it doesn't look quite right or work yet, it won't until we import the interface records in the next step.

If you want to filter the hierarchy as we do in Example Two, you can copy the whole "begins
with..." blue pill from our example two layout and paste that on to your layout as well. If you're interested in [[using example three]] you can move on to that after you complete the next step below.
to:
Now that you've got all the necessary scripts in place, you're ready to add the contents of the Hierarchy layout (from Example One, Two, or Three). Select all of the layout elements from the Hierarchy layout in SeedCodeHierarchy.fp7 and then move to the Hierarchy layout in your file, removing the Header and Footer parts, if any. Then paste the layout elements into your layout. Don't worry if it doesn't look quite right or work yet: it won't until we import the interface records in the next step.

If you want to filter the hierarchy as we do in Example Two, you can copy the whole "begins
with..." blue pill from our Example Two layout and paste that on to your layout as well. If you're interested in [[using example three]] you can move on to that after you complete the next step below.
Changed lines 91-92 from:
If you want to be able to [[new item | create new items]] in your data tables from the hierarchy, you'll need to edit these layouts just a bit: on each layout, place all the key fields for that table. So in our sample data you'll see that for Level2 we have two fields there, the primary key for the table ("ProjectID_kprime") and the foreign key we link to Companies ("ProjectCompanyID_kf"). Add each table's key fields to each of the "Level.." layouts and make sure the fields are enterable in browse mode.
to:
If you want to be able to [[new item | create new items]] in your data tables from the hierarchy, you'll need to edit these layouts just a bit: on each layout, place all the key fields for that layout's table. So in our sample data you'll see that for Level2 we have two fields there, the primary key for the table ("ProjectID_kprime") and the foreign key we link to Companies ("ProjectCompanyID_kf"). Add each table's key fields to each of the "Level.." layouts and make sure the fields are enterable in browse mode.
Changed lines 73-78 from:
If you want to show the details of selected items as we do in Example Three, you'll go a little further. See [[Using Example Three]] for more information.

'''8. Editing the DisplayContents... Fields.'''

In step 5 we left a few fields that were commented out and we
'll now return to fix those. Open the field definition for the field DisplayContentsLevel1Calc in your file and remove the leading and trailing comments (remove the /* at the beginning of the calc and the */ at the end of the calc). Now edit the field definition itself, adding the fields you'd like to see depict your level 1 record: in our example this would be "HierarchyPortalLevel1::CompanyName" (without the quotes). Note the the fields from your top level table should come from HierarchyPortalLevel1 and that the calculation should be defined from the perspective of Hierarchy.
to:
If you want to show the details of selected items as we do in Example Three, you'll go a little further. See [[Using Example Three]] for more information. (You'll want to complete steps 1 and 2 of those [[Using Example Three | instructions]] before continuing.)

'''8. Editing the "DisplayContents..." Fields.'''

In step 5 we left a few fields that were commented out
and we'll now return to fix those. Open the field definition for the field "DisplayContentsLevel1Calc" in your file and remove the leading and trailing comments (remove the /* at the beginning of the calc and the */ at the end of the calc). Now edit the field definition itself, adding the fields you'd like to see depict your level 1 record: in our example this would be "HierarchyPortalLevel1::CompanyName" (without the quotes). Note that the fields from your top level table should come from "HierarchyPortalLevel1" and that the calculation should be defined from the perspective of "Hierarchy".
Changed lines 87-88 from:
Next, create one blank layout for each of your data levels. These will be named "HierarchyLevel1", "HierarchyLevel2",etc. and will be based on the "data" table occurrences you created in step 3 above. So the layout "HierarchyLevel1" will show records from "HierarchyDataLevel1", etc.
to:
Next, create one blank layout for each of your data levels. These will be named "HierarchyLevel1", "HierarchyLevel2",etc. and will be based on the "data" table occurrences you created in step 3 above. So the layout "HierarchyLevel1" will show records from "HierarchyDataLevel1", etc.:
Changed lines 39-40 from:
If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields one at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields DisplayContentsLevel1Calc, ...Level2Calc, etc can't be entered by hand yet: we'll tackle those in the next two steps.)
to:
If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields one at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields DisplayContentsLevel1Calc, ...Level2Calc, etc. can't be entered by hand yet: we'll tackle those in the next two steps.)
Changed lines 43-44 from:
If you see more errors than these (i.e. more fields commented out) you may have slightly different names for your "Hierarchy" and "HierarchyPortalLevel1" etc. table occurrences. If that is the case, delete the newly pasted fields, correct the names of your TOs and try again.
to:
If you see more errors than these (i.e. more fields commented out) you may have slightly different names for your "Hierarchy" and "HierarchyPortalLevel1" etc. table occurrences. If that's the case, delete the newly pasted fields, correct the names of your TOs and try again.
Changed lines 59-60 from:
Move to the relationship graph in your file and connect the TO  "Hierarchy Portal" to "HierarchyPortalLevel1". Link "Level1KeyCalc" in "Hierarchy Portal" to the primary key field in "HierarchyPortalLevel1": in our example that would be the CompanyID field.
to:
Move to the relationship graph in your file and connect the TO  "Hierarchy Portal" to "HierarchyPortalLevel1" by linking "Level1KeyCalc" in "Hierarchy Portal" to the primary key field in "HierarchyPortalLevel1": in our example that would be the CompanyID field.
Changed lines 3-6 from:
SeedCode Hierarchy is made to be used with your own files: you can teach the hierarchy about our own tiered structures and see your records within the hierarchy. You'll actually add the hierarchy code to your file so that SeedCode Hierrachy.fp7 doesn't have to be part of your solution and can be something you use just for reference: the whole hierarchy will be ''in'' your file. The following instructions will walk you through this step-by-step.

!! About FileMaker Advanced
to:
SeedCode Hierarchy is made to be used with your own files: you can teach the hierarchy about your own tiered structures and see ''your'' records within the hierarchy. You'll actually add the hierarchy code to your file so that SeedCode Hierrachy.fp7 doesn't have to be part of your solution and can be something you use just for reference: the whole hierarchy will be ''in'' your file. The following instructions will walk you through this step-by-step.

!! Using FileMaker Advanced?
Changed lines 17-18 from:
Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A Table Occurrence (TO) for this will be added to your relationship graph  (File / Manage / Database... and the click on "Relationships"). Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them alone on your relationship graph.
to:
Create a new table in your file called "Hierarchy"; this doesn't need to have any fields associated with it yet, so just make the table and nothing else. A Table Occurrence (TO) for this will be added to your relationship graph  (File / Manage / Database... and the click on "Relationships"). Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to relate these two to anything, just leave them alone on your relationship graph.
Changed lines 27-28 from:
So make a simple Table Occurrence Group (TOG) for use in the hierarchy and relate your version of Companies, Projects, and Tasks to each other as naturally as possible, even is you're using [[SelfJoins | self-joins or join tables]]. Then, rename the table occurrences so that the top-level TO (Companies in our example) is named "HierarchyDataLevel1" (without the quotes), the next one down is "HierarchyDataLevel2", etc. You'll find a TOG like this in the relationship graph of SeedCode Hierarchy and make sure you match the TO names used there exactly.
to:
So make a simple Table Occurrence Group (TOG) for use in the hierarchy and relate your version of Companies, Projects, and Tasks to each other as naturally as possible, even is you're using [[SelfJoins | self-joins or join tables]]. Then, rename the table occurrences so that the top-level TO (Companies, in our example) is named "HierarchyDataLevel1" (without the quotes), the next one down is "HierarchyDataLevel2", etc. You'll find a TOG like this in the relationship graph of SeedCodeHierarchy.fp7 and make sure you match the TO names used there exactly.
Changed lines 87-88 from:
Next, create one blank layout for each of your data levels. These will be named "Level1", "Level2",etc. and will be based on the "data" table occurrences you created in step 3 above. So the layout "Level1" will show records from "HierarchyDataLevel1", etc.
to:
Next, create one blank layout for each of your data levels. These will be named "HierarchyLevel1", "HierarchyLevel2",etc. and will be based on the "data" table occurrences you created in step 3 above. So the layout "HierarchyLevel1" will show records from "HierarchyDataLevel1", etc.
Changed lines 99-100 from:
-> Edit the script "Set default contents". This script controls the default contents of the hierarchy, controlling which records show up when you first arrive. It currently sets the variable $$Hy_Show to 15 to show the first 15 top-level records in our demo. You'll likely just want to replace "15" with "All" to show all your top-level records. The script itself contains instructions for going further and [[UsingExampleTwo | filtering]] the hierarchy by default.
to:
-> Edit the script "Set Default Contents". This script controls the default contents of the hierarchy, controlling which records show up when you first arrive. It currently sets the variable $$Hy_Show to 15 to show the first 15 top-level records in our demo. You'll likely just want to replace "15" with "All" to show all your top-level records. The script itself contains instructions for going further and [[UsingExampleTwo | filtering]] the hierarchy by default.
Added lines 99-100:
-> Edit the script "Set default contents". This script controls the default contents of the hierarchy, controlling which records show up when you first arrive. It currently sets the variable $$Hy_Show to 15 to show the first 15 top-level records in our demo. You'll likely just want to replace "15" with "All" to show all your top-level records. The script itself contains instructions for going further and [[UsingExampleTwo | filtering]] the hierarchy by default.
Changed lines 107-108 from:
If your file doesn't have a script that runs on file open (Fie / File Options), you can use the "Upon Opening" script you imported from the Hierarchy. If you already have one, add a Perform Script line to your opening script to call ours at some point. In either case, you'll find a comment in the script beginning "Remove the following two lines...". Be sure to do that and delete the line that sets the $$Hy_Show variable. You may also want to delete one or both of the following "Perform Script..." lines if you won't be showing the hierarchy as soon as the file opens.
to:
If your file doesn't have a script that runs on file open (Fie / File Options), you can use the "Upon Opening" script you imported from the Hierarchy. If you already have one, add a Perform Script line to your opening script to call ours at some point. You may want to delete these last two PerformScript() lines from our "Upon Opening" script if you're not showing the hierarchy right away.
Changed lines 27-28 from:
So make a simple Table Occurrence Group (TOG) for use in the hierarchy and relate your version of Companies, Projects, and Tasks to each other as naturally as possible. Then, rename the table occurrences so that the top-level TO (Companies in our example) is named "HierarchyDataLevel1" (without the quotes), the next one down is "HierarchyDataLevel2", etc. You'll find a TOG like this in the relationship graph of SeedCode Hierarchy and make sure you match the TO names used there exactly.
to:
So make a simple Table Occurrence Group (TOG) for use in the hierarchy and relate your version of Companies, Projects, and Tasks to each other as naturally as possible, even is you're using [[SelfJoins | self-joins or join tables]]. Then, rename the table occurrences so that the top-level TO (Companies in our example) is named "HierarchyDataLevel1" (without the quotes), the next one down is "HierarchyDataLevel2", etc. You'll find a TOG like this in the relationship graph of SeedCode Hierarchy and make sure you match the TO names used there exactly.
Changed lines 91-92 from:
If you want to be able to [[new item | create new items]] in your data tables from the hierarchy, you'll need to edit these layouts just a bit: on each layout, place all the key fields for that table. So in our sample data you'll see that for Level2 we have two fields there, the primary key for te table ("ProjectID_kprime") and the foreign key we link to Companies ("ProjectCompanyID_kf"). Add each table's key fields to each of the "Level.." layouts and make sure the fields are enterable in browse mode.
to:
If you want to be able to [[new item | create new items]] in your data tables from the hierarchy, you'll need to edit these layouts just a bit: on each layout, place all the key fields for that table. So in our sample data you'll see that for Level2 we have two fields there, the primary key for the table ("ProjectID_kprime") and the foreign key we link to Companies ("ProjectCompanyID_kf"). Add each table's key fields to each of the "Level.." layouts and make sure the fields are enterable in browse mode.
Changed lines 105-106 from:
If your file doesn't have a script that runs on file open (Fie / File Options), you can use the "Upon Opening" script you imported from the Hierarchy. If you already have one, add a Perform Script line to your opening script to call ours at some point. In either case, you'll find a comment in the script beginning "Remoe the following two lines...". Be sure to do that and delete the line that sets the $$Hy_Show variable. You may also want to delete one or both of the following "Perform Script..." lines if you won't be showing the hierarchy as soon as the file opens.
to:
If your file doesn't have a script that runs on file open (Fie / File Options), you can use the "Upon Opening" script you imported from the Hierarchy. If you already have one, add a Perform Script line to your opening script to call ours at some point. In either case, you'll find a comment in the script beginning "Remove the following two lines...". Be sure to do that and delete the line that sets the $$Hy_Show variable. You may also want to delete one or both of the following "Perform Script..." lines if you won't be showing the hierarchy as soon as the file opens.
Changed lines 3-4 from:
SeedCode Hierarchy is made to be used with your own files: you can teach the hierarchy about our own tiered structures and see your records within the hierarchy. You'll actually add the hierarchy code to your file so that SeedCode Hierrachy.fp7 doesn't have to be part of your solution and can be something you use just for reference: the whole hierarchy will be ''in'' your file. The following instructions will  walk you through this step-by-step.
to:
SeedCode Hierarchy is made to be used with your own files: you can teach the hierarchy about our own tiered structures and see your records within the hierarchy. You'll actually add the hierarchy code to your file so that SeedCode Hierrachy.fp7 doesn't have to be part of your solution and can be something you use just for reference: the whole hierarchy will be ''in'' your file. The following instructions will walk you through this step-by-step.
Changed lines 7-8 from:
Moving SeedCode Hierarchy into your file is much easier if you have FileMaker Advanced, since it allows you to copy and paste field definitions between files. You can integrate the hierarchy without Advanced, it is just a bit more work. So if you don't have [[http://www.filemaker.com/products/fmpa/index.html | FileMaker Advanced]], consider getting a copy: you'll appreciate it. Otherwise, feel free to contact SeedCode, we can do this integration for you in just XXXXX.
to:
Moving SeedCode Hierarchy into your file is much easier if you have FileMaker Advanced, since it allows you to copy and paste field definitions between files. You can integrate the hierarchy without Advanced, it is just a bit more work. So if you don't have [[http://www.filemaker.com/products/fmpa/index.html | FileMaker Advanced]], consider getting a copy: you'll appreciate it. Otherwise, feel free to [[ http://http://www.seedcode.com/cp-app/contact/1 | contact]] SeedCode, we can get you a fixed price to do this integration for you.
Changed lines 1-2 from:
!! Overview
to:
!! Overview: Adding the Hierarchy to Your File
October 05, 2008, at 09:26 PM by 67.183.22.167 -
October 05, 2008, at 09:26 PM by 67.183.22.167 -
Changed lines 85-86 from:
First, create a new layout in your file called "Hierarchy" and base it on the Hierarchy table occurrence. (This layout may have been created for you in step 1 above: if so, just delete all the fields from it so you have an empty layout and move on.) You may not use this down the road as you can include the hierarchy on any layout in your file, but the layout name is used in our scripts and you'll likely want to keep this layout around as a test layout for making sure the hierarchy works and making changes to it.
to:
First, create a new layout in your file called "Hierarchy" and base it on the Hierarchy table occurrence. (This layout may have been created for you in step 1 above: if so, just delete all the fields from it so you have an empty layout and move on.) You may not end up using this down the road as you can [[HierarchyOnYourLayouts | include the hierarchy on any layout in your file]], but the layout name is used in our scripts and you'll likely want to keep this layout around as a test layout for making sure the hierarchy works and making changes to it.
Changed lines 69-70 from:
%center% %width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
Added lines 91-92:
If you want to be able to [[new item | create new items]] in your data tables from the hierarchy, you'll need to edit these layouts just a bit: on each layout, place all the key fields for that table. So in our sample data you'll see that for Level2 we have two fields there, the primary key for te table ("ProjectID_kprime") and the foreign key we link to Companies ("ProjectCompanyID_kf"). Add each table's key fields to each of the "Level.." layouts and make sure the fields are enterable in browse mode.
Changed lines 97-98 from:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example two. Scroll toward the end of the script and you'll see a comment that begins "Specify the Target Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top level table. In our example this was the company name field, but yiu may wish to filter differently. Note that you can branch this script later to [[ Found Sets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.
to:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example two. Scroll toward the end of the script and you'll see a comment that begins "Specify the Target Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top level table. In our example this was the company name field, but you may wish to filter differently. Note that you can branch this script later to [[ Found Sets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.
Added lines 103-104:
If your file doesn't have a script that runs on file open (Fie / File Options), you can use the "Upon Opening" script you imported from the Hierarchy. If you already have one, add a Perform Script line to your opening script to call ours at some point. In either case, you'll find a comment in the script beginning "Remoe the following two lines...". Be sure to do that and delete the line that sets the $$Hy_Show variable. You may also want to delete one or both of the following "Perform Script..." lines if you won't be showing the hierarchy as soon as the file opens.
Changed lines 17-18 from:
Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them alone on your relationship graph.
to:
Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A Table Occurrence (TO) for this will be added to your relationship graph  (File / Manage / Database... and the click on "Relationships"). Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them alone on your relationship graph.
Changed lines 67-68 from:
Now connect Hierarchy to Hierarchy Portal, using PortalKeyCalc on the Hierarchy side, and RecordNumber on the HierarchyPortal side. Use the ">" operator so that PortalKeyCalc > RecordNumber.
to:
Now connect Hierarchy to Hierarchy Portal, using PortalKeyCalc on the Hierarchy side, and RecordNumber on the HierarchyPortal side. Use the ">" operator so that PortalKeyCalc "is greater than" RecordNumber.
Changed lines 63-64 from:
%center% %width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs1.png
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs1.png
Changed lines 69-70 from:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
to:
%center% %width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
Changed lines 63-64 from:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs1.png
to:
%center% %width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs1.png
Changed lines 89-90 from:
%center%  %width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/layouts.png
to:
%center%  http://www.seedcode.com/rootimages/stikipad/hierarchy/layouts.png
Changed lines 69-70 from:
%center% %Width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
Changed lines 89-90 from:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/layouts.png
to:
%center%  %width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/layouts.png
Changed lines 69-70 from:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
to:
%center% %Width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
Changed lines 69-70 from:
%center% %width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
Changed lines 69-70 from:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
to:
%center% %width=500% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
Changed lines 39-40 from:
If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields on at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields DisplayContentsLevel1Calc, ...Level2Calc, etc can't be entered by hand yet: we'll tackle those in the next two steps.)
to:
If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields one at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields DisplayContentsLevel1Calc, ...Level2Calc, etc can't be entered by hand yet: we'll tackle those in the next two steps.)
Changed lines 55-56 from:
to:
Add the fields from HierarchyInterface the same way. These are simple container globals and there are no special options to worry about with them.
Added lines 119-120:
When you created your HierarchyInterface table, FileMaker added a layout for this to your file. Navigate to that layout and select "Import Records... / File" from FileMaker's File menu and select SeedCode Hierarchy as the file to import from. Make sure the table on the left side of the import (the SeedCode Hierarchy side) is set to use the HierarchyInterface table, and that the import order is set to use "matching names". Then import the 1 interface record.
Added lines 19-20:
Now create a table called "HierarchyInterface" and leave it alone on your graph as well; we'll add fields to it later.
Added lines 98-99:
-> Edit the script "Go to Item". You'll see several "Go to Related Record..." steps there. Edit the step for each level to indicate the layout in your file that you'd like to use when viewing records. This is part of the routine we run when clicking on the green arrow in the hierarchy to go to an item in form view.
Deleted line 44:
-> ArrowImageDisplayCalc
Changed lines 51-52 from:

to:
-> OpenCloseArrowDisplayCalc

Changed lines 94-95 from:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example two. Scroll toward the end of the script and you'll see a comment that begins "Replace the Set Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top level table. In our example this was the company name field, but yiu may wish to filter differently. Note that you can branch this script later to [[ Found Sets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.
to:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example two. Scroll toward the end of the script and you'll see a comment that begins "Specify the Target Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top level table. In our example this was the company name field, but yiu may wish to filter differently. Note that you can branch this script later to [[ Found Sets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.
Changed lines 102-103 from:
Now that you've got all the necessary scripts in place you're ready to add the contents of the Hierarchy layout. Select all of the layout elements from the Hierarchy layout in SeedCode Hierarchy and then move to the Hierarch layout in your file, removing the Header and Footer parts, if any. Then paste the layout elements into your layout.
to:
Now that you've got all the necessary scripts in place you're ready to add the contents of the Hierarchy layout (from Example One). Select all of the layout elements from the Hierarchy layout in SeedCode Hierarchy and then move to the Hierarch layout in your file, removing the Header and Footer parts, if any. Then paste the layout elements into your layout. Don't worry if it doesn't look quite right or work yet, it won't until we import the interface records in the next step.

If you want to filter the hierarchy as we do in Example Two, you can copy the whole "begins with..." blue pill from our example two layout and paste that on to your layout as well. If you're interested in [[using example three]] you can move on to that after you complete the next step below
.
Changed lines 110-112 from:
The hierarchy uses 5000 place holder records to depict the records in your file. These record's aren't ''data'' per se, and they don't take up much room. You'll need to import these records into your file in order to get the hierarchy working, and to bring the hierarchy's interface to life.

From the Hierarchy layout in your file, select "Import Records... / File" from FileMaker's File menu and select SeedCode Hierarchy as the file to import from. Make sure the table on the left side of the import (the SeedCode Hierarchy side) is set to use the Hierarchy table, and that the import order is set to use "matching names". Then import the 5000 records, marking the "perform auto enter..." checkbox as yes.
to:
The hierarchy uses 5000 place holder records to depict the records in your tables. These record's aren't ''data'' per se, and they don't take up much room. You'll need to import these records into your file in order to get the hierarchy working, and to bring the hierarchy's interface to life.

From the Hierarchy layout in your file, select "Import Records... / File" from FileMaker's File menu and select SeedCode Hierarchy as the file to import from. Make sure the table on the left side of the import (the SeedCode Hierarchy side) is set to use the Hierarchy table, and that the import order is set to use "matching names". Then import the 5000 records, marking the "perform auto enter..." checkbox as yes.

That's it! Your hierarchy is all set to go. Click the "show hierarchy" button to load your records in and then have fun!
Changed lines 94-95 from:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example two. Scroll toward the end of the script and you'll see a comment that begins "Replace the Set Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top level table. In our example this was the company name field, but yiu may wish to filter differently. Note that you can branch this script later to [[ foundsets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.
to:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example two. Scroll toward the end of the script and you'll see a comment that begins "Replace the Set Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top level table. In our example this was the company name field, but yiu may wish to filter differently. Note that you can branch this script later to [[ Found Sets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.
Changed lines 94-95 from:
-> Edit the script "Build Found Set for Top Level". In there you'll find a couple of examples of different searches you can perform to "filter" the contents of the hierarchy to just one kind of record in the hierarchy's top level. Double click on each "Perform Find" script step and adjust the find criteria so that it makes sense for your solution. You may choose not to use any find criteria in which case you can leave these script steps alone as you'll be using the "Show All Records" option instead.
to:
-> Edit the script "Build Found Set for Top Level". This script controls which top level records show up in the hierarchy. And the only section you have to edit is the part where we "filter" the hierarchy as shown in Example two. Scroll toward the end of the script and you'll see a comment that begins "Replace the Set Field below with the field in your top level table...". Highlight the next script step (Set Field) and change the target field to the field you'd like to search on in your top level table. In our example this was the company name field, but yiu may wish to filter differently. Note that you can branch this script later to [[ foundsets | show different found sets of top level records ]]. Editing that one set field is all you need to do this this script.
Added lines 86-87:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/layouts.png
Changed lines 70-71 from:
If you want to show the details of selected items as we do in Example Three, you'll also connect the table occurrences HierarchyPortalSelectedItemLevel1, HierarchyPortalSelectedItemLevel2, etc. to the field "SelectedItemIDGlob" as we've done in our graph. See [[Using Example Three]] for more information.
to:
If you want to show the details of selected items as we do in Example Three, you'll go a little further. See [[Using Example Three]] for more information.
Changed lines 82-85 from:
First, create a new layout in your file called "Hierarchy" and base it on the Hierarchy table occurrence. (This layout may have been created for you in step 1 above: if so, just delete all the fields from it and move on.) You may not use this down the road as you can include the hierarchy on any layout in your file, but the layout name is used in our scripts and you'll likely want to keep this layout around as a test layout for making sure the hierarchy works and making changes to it.

Next, create one blank layout for each of your data levels. These will be named "Level1", "Level2",etc
. and will be based on the "date" table occurrences you created in step 3 above. So the layout "Level1" will show records from "HierarchyDataLevel1", etc.
to:
First, create a new layout in your file called "Hierarchy" and base it on the Hierarchy table occurrence. (This layout may have been created for you in step 1 above: if so, just delete all the fields from it so you have an empty layout and move on.) You may not use this down the road as you can include the hierarchy on any layout in your file, but the layout name is used in our scripts and you'll likely want to keep this layout around as a test layout for making sure the hierarchy works and making changes to it.

Next, create one blank layout for each of your data levels
. These will be named "Level1", "Level2",etc. and will be based on the "data" table occurrences you created in step 3 above. So the layout "Level1" will show records from "HierarchyDataLevel1", etc.
Changed lines 31-32 from:
Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the phrase "PortalSelectedItem" so that the Companies TO (in our example) would be named "HierarchyPortalSelectedItemLevel1" (without the quotes), Projects would be "HierarchyPortalSelectedItemLevel2", etc. When you're done, this section of your relationship graph should look like this:
to:
Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:
Changed lines 68-69 from:
That's it. Those are all the changes you need to make to your relationship graph.
to:
That's it. Those are all the changes you need to make to your relationship graph in order to get the hierarchy to display.

If you want to show the details of selected items as we do in Example Three, you'll also connect the table occurrences HierarchyPortalSelectedItemLevel1, HierarchyPortalSelectedItemLevel2, etc. to the field "SelectedItemIDGlob" as we've done in our graph. See [[Using Example Three]] for more information
.
Changed lines 60-61 from:
<< image >>
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs1.png
Changed lines 66-67 from:
<< image >>
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/connectingTOs2.png
Changed lines 43-44 from:
Note. You'll want to double check that all the calculation fields you've pasted are define from the correct context. (The context of a calc is shown in the "Evaluate this calculation from the context of.." menu at the very top of the calculation entry screen. The following calcs should be defined from the context of "HierarchyPortal", the remainder from the context of "Hierarchy":
to:
Note. You'll want to double check that all the calculation fields you've pasted are defined from the correct context. (The context of a calc is shown in the "Evaluate this calculation from the context of.." menu at the very top of the calculation entry screen.) The following calcs should be defined from the context of "HierarchyPortal", the remainder from the context of "Hierarchy":
Changed lines 54-55 from:
'''6. Linking "Hierarchy Portal" to "HierarchyPortalLevel1", "...Level2", etc.''' 
to:
'''6. Linking Table Occurrences: "Hierarchy Portal" to "HierarchyPortalLevel1", "...Level2", etc.''' 
Changed lines 31-32 from:
Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:
to:
Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the phrase "PortalSelectedItem" so that the Companies TO (in our example) would be named "HierarchyPortalSelectedItemLevel1" (without the quotes), Projects would be "HierarchyPortalSelectedItemLevel2", etc. When you're done, this section of your relationship graph should look like this:
Changed lines 33-34 from:
<< image >>
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/portalTOs.png
Changed lines 27-28 from:
<< image >>
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/dataTOs.png
Changed lines 19-20 from:
%center% http://www.seedcode.com/rootimages/homepage/wordle_integration.png
to:
%center% http://www.seedcode.com/rootimages/stikipad/hierarchy/hierarchyTOs.png
Changed lines 19-20 from:
<< image >>
to:
%center% http://www.seedcode.com/rootimages/homepage/wordle_integration.png
Changed lines 17-18 from:
Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them along on your relationship graph.
to:
Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them alone on your relationship graph.
August 17, 2008, at 09:44 PM by 76.28.195.40 -
Added lines 43-53:
Note. You'll want to double check that all the calculation fields you've pasted are define from the correct context. (The context of a calc is shown in the "Evaluate this calculation from the context of.." menu at the very top of the calculation entry screen. The following calcs should be defined from the context of "HierarchyPortal", the remainder from the context of "Hierarchy":

-> ArrowImageDisplayCalc
-> DisplayContentsLevel1Calc
-> DisplayContentsLevel2Calc
-> DisplayContentsLevel3Calc
-> DisplayContentsLevel4Calc
-> DisplayContentsLevel5Calc
-> ItemDisplayCalc

August 17, 2008, at 08:56 PM by 76.28.195.40 -
Changed lines 37-38 from:
If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields on at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields 'DisplayContentsLevel1Calc, ...Level2Calc, etc can't be entered by hand yet: we'll tackle those in the next two steps.)
to:
If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields on at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields DisplayContentsLevel1Calc, ...Level2Calc, etc can't be entered by hand yet: we'll tackle those in the next two steps.)
Added lines 51-56:
'''7. Linking Hierarchy to Hierarchy Portal.'''

Now connect Hierarchy to Hierarchy Portal, using PortalKeyCalc on the Hierarchy side, and RecordNumber on the HierarchyPortal side. Use the ">" operator so that PortalKeyCalc > RecordNumber.

<< image >>

Added lines 59-64:
'''8. Editing the DisplayContents... Fields.'''

In step 5 we left a few fields that were commented out and we'll now return to fix those. Open the field definition for the field DisplayContentsLevel1Calc in your file and remove the leading and trailing comments (remove the /* at the beginning of the calc and the */ at the end of the calc). Now edit the field definition itself, adding the fields you'd like to see depict your level 1 record: in our example this would be "HierarchyPortalLevel1::CompanyName" (without the quotes). Note the the fields from your top level table should come from HierarchyPortalLevel1 and that the calculation should be defined from the perspective of Hierarchy.

Continue in this manner with each of the "DisplayContentsLevel..." calcs, choosing which content to display for each level. Note that you have a lot of control over the [[text formatting]] of the hierarchy, so be creative.

Changed lines 67-68 from:
'''7. Creating Layouts in Your File.'''
to:
'''9. Creating Layouts in Your File.'''
Changed lines 75-76 from:
'''8. Importing Scripts.'''
to:
'''10. Importing Scripts.'''
Changed lines 85-86 from:
'''9. Pasting in the Hierarchy Layout.'''
to:
'''11. Pasting in the Hierarchy Layout.'''
Changed lines 91-92 from:
'''10. Import the Hierarchy's Interface Records.'''
to:
'''12. Import the Hierarchy's Interface Records.'''
August 17, 2008, at 08:34 PM by 76.28.195.40 -
Changed lines 75-83 from:
Now that you've got all the necessary scripts in place you're ready to add the contents of the Hierarchy layout. Select all of the layout elements from the Hierarchy layout in SeedCode Hierarchy and then move to the Hierarch layout in your file, removing the Header and Footer parts, if any. Then paste the layout elements into your layout.
to:
Now that you've got all the necessary scripts in place you're ready to add the contents of the Hierarchy layout. Select all of the layout elements from the Hierarchy layout in SeedCode Hierarchy and then move to the Hierarch layout in your file, removing the Header and Footer parts, if any. Then paste the layout elements into your layout.

!! Almost Done: Importing Records

'''10. Import the Hierarchy's Interface Records.'''

The hierarchy uses 5000 place holder records to depict the records in your file. These record's aren't ''data'' per se, and they don't take up much room. You'll need to import these records into your file in order to get the hierarchy working, and to bring the hierarchy's interface to life.

From the Hierarchy layout in your file, select "Import Records... / File" from FileMaker's File menu and select SeedCode Hierarchy as the file to import from. Make sure the table on the left side of the import (the SeedCode Hierarchy side) is set to use the Hierarchy table, and that the import order is set to use "matching names". Then import the 5000 records, marking the "perform auto enter..." checkbox as yes
.
August 17, 2008, at 08:29 PM by 76.28.195.40 -
Changed line 75 from:
Now that you've got all the necessary scripts in place you're ready to add the contents of the Hierarchy layout.
to:
Now that you've got all the necessary scripts in place you're ready to add the contents of the Hierarchy layout. Select all of the layout elements from the Hierarchy layout in SeedCode Hierarchy and then move to the Hierarch layout in your file, removing the Header and Footer parts, if any. Then paste the layout elements into your layout.
August 17, 2008, at 03:19 AM by 76.28.195.40 -
Changed lines 65-66 from:
If you're using FileMaker Advanced, open ScriptMaker in your file and import all of the scripts from SeedCodeHierarchy.fp7 into your file. You'll see two sections of scripts within the "Hierarchy" section and you'll only need to edit the script that are in the "Data Scripts" section-- and you'll find that these edits are very simple.
to:
Open ScriptMaker in your file and import all of the scripts from SeedCodeHierarchy.fp7 into your file. You'll see two sections of scripts within the "Hierarchy" section and you'll only need to edit the script that are in the "Data Scripts" section-- and you'll find that these edits are very simple.
August 17, 2008, at 03:14 AM by 76.28.195.40 -
August 17, 2008, at 03:14 AM by 76.28.195.40 -
Added lines 71-75:
!! Layouts Part 2

'''9. Pasting in the Hierarchy Layout.'''

Now that you've got all the necessary scripts in place you're ready to add the contents of the Hierarchy layout.
August 17, 2008, at 03:07 AM by 76.28.195.40 -
Changed lines 69-70 from:
-> Edit the script that begin "Sort Level...". Each script contains only one step and is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each level.
to:
-> Edit the script that begin "Sort Level...". Each script contains only one step and is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field(s) you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each level.
August 17, 2008, at 02:59 AM by 76.28.195.40 -
Changed lines 67-70 from:
--> Edit the script "Build Found Set for Top Level". In there you'll find a couple of examples of different searches you can perform to "filter" the contents of the hierarchy to just one kind of record in the hierarchy's top level. Double click on each "Perform Find" script step and adjust the find criteria so that it makes sense for your solution. You may choose not to use any find criteria in which case you can leave these script steps alone as you'll be using the "Show All Records" option instead.

--> Edit the script that begin "Sort Level...". Each script contains only one step and is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each level.
to:
-> Edit the script "Build Found Set for Top Level". In there you'll find a couple of examples of different searches you can perform to "filter" the contents of the hierarchy to just one kind of record in the hierarchy's top level. Double click on each "Perform Find" script step and adjust the find criteria so that it makes sense for your solution. You may choose not to use any find criteria in which case you can leave these script steps alone as you'll be using the "Show All Records" option instead.

-> Edit the script that begin "Sort Level...". Each script contains only one step and is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each level.
August 17, 2008, at 02:59 AM by 76.28.195.40 -
August 17, 2008, at 02:58 AM by 76.28.195.40 -
Changed lines 65-69 from:
If you're using FileMaker Advanced, open ScriptMaker in your file and import all of the scripts from SeedCodeHierarchy.fp7 into your file. You'll see two sections of scripts within the "Hierarchy" section and you'll only need to edit the script that are in the "Data Scripts" section-- and you'll find that these edits are very simple.

->
Edit the script that begin "Sort Level...". Each script contains only one step and is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each level.

->
to:
If you're using FileMaker Advanced, open ScriptMaker in your file and import all of the scripts from SeedCodeHierarchy.fp7 into your file. You'll see two sections of scripts within the "Hierarchy" section and you'll only need to edit the script that are in the "Data Scripts" section-- and you'll find that these edits are very simple.

-->
Edit the script "Build Found Set for Top Level". In there you'll find a couple of examples of different searches you can perform to "filter" the contents of the hierarchy to just one kind of record in the hierarchy's top level. Double click on each "Perform Find" script step and adjust the find criteria so that it makes sense for your solution. You may choose not to use any find criteria in which case you can leave these script steps alone as you'll be using the "Show All Records" option instead.

--> Edit the script that begin
"Sort Level...". Each script contains only one step and is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each level.
August 17, 2008, at 02:56 AM by 76.28.195.40 -
Changed lines 65-69 from:
If you're using
to:
If you're using FileMaker Advanced, open ScriptMaker in your file and import all of the scripts from SeedCodeHierarchy.fp7 into your file. You'll see two sections of scripts within the "Hierarchy" section and you'll only need to edit the script that are in the "Data Scripts" section-- and you'll find that these edits are very simple.

-> Edit the script that begin "Sort Level...". Each script contains only one step and is used to determine the [[sort order]] in which a record's peers appear in the hierarchy. In each script, double click on the "Sort Records" script step to change the sort order. Make sure the table at the top of the field list says "HierarchyDataLevel1" and then pick the field you'd like to sort your records by: in our example this would be the field ""HierarchyDataLevel1::CompanyName". Repeat this for the sort scripts for each level, making sure to select fields from the "HierarchyDataLevel..." TO appropriate to each level.

->
August 17, 2008, at 01:20 AM by 76.28.195.40 -
Changed lines 29-30 from:
'''4. Create a Second Version of this TOG.
to:
'''4. Create a Second Version of this TOG.'''
August 17, 2008, at 01:20 AM by 76.28.195.40 -
Changed lines 11-16 from:
'''1.''' Backup your files. 

Really.

'''2.''' Create a New Table. 
to:
'''1. Backup your files.'''

Really
. ;-)

'''2.
Create a New Table.'''
Changed lines 21-22 from:
'''3.''' Create a Representation of Your Data on the Graph.
to:
'''3. Create a Representation of Your Data on the Graph.'''
Changed lines 29-30 from:
'''4.''' Create a Second Version of this TOG.
to:
'''4. Create a Second Version of this TOG.
Changed lines 35-36 from:
'''5.''' Pasting in Field Definitions.
to:
'''5. Pasting in Field Definitions.'''
Changed lines 43-44 from:
'''6.''' Linking "Hierarchy Portal" to "HierarchyPortalLevel1", "...Level2", etc. 
to:
'''6. Linking "Hierarchy Portal" to "HierarchyPortalLevel1", "...Level2", etc.''' 
Changed lines 55-56 from:
'''7.''' Creating Layouts in Your File.
to:
'''7. Creating Layouts in Your File.'''
Changed lines 63-64 from:
'''8.''' Importing Scripts
to:
'''8. Importing Scripts.'''
August 17, 2008, at 01:18 AM by 76.28.195.40 -
Changed lines 51-65 from:
to:
That's it. Those are all the changes you need to make to your relationship graph.

!! Layouts Part 1

'''7.''' Creating Layouts in Your File.

First, create a new layout in your file called "Hierarchy" and base it on the Hierarchy table occurrence. (This layout may have been created for you in step 1 above: if so, just delete all the fields from it and move on.) You may not use this down the road as you can include the hierarchy on any layout in your file, but the layout name is used in our scripts and you'll likely want to keep this layout around as a test layout for making sure the hierarchy works and making changes to it.

Next, create one blank layout for each of your data levels. These will be named "Level1", "Level2",etc. and will be based on the "date" table occurrences you created in step 3 above. So the layout "Level1" will show records from "HierarchyDataLevel1", etc.

!! Scripts

'''8.''' Importing Scripts

If you're using
August 17, 2008, at 01:04 AM by 76.28.195.40 -
August 17, 2008, at 01:04 AM by 76.28.195.40 -
Changed lines 11-14 from:
'''1.''' Backup your files. Really.

'''2.''' Create a New Table. Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them along on your relationship graph.
to:
'''1.''' Backup your files.

Really.

'''2.''' Create a New Table.

Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them along on your relationship graph.
Changed lines 21-22 from:
'''3.''' Create a Representation of Your Data on the Graph. Create new table occurrences on your relationship graph to represent the data you'd like to see in the hierarchy. (Don't worry about having [[multiple hierarchies]] at this point, you can come back to that later.) In our example we have Companies, Projects, and Tasks, and each of these is related to each other as you'd expect: Companies and Projects by CompanyID, then Projects and Tasks by Project ID. You may already have a section of your relationship graph which depicts this "natural" relationship between your tables, but you'll need a separate one for the hierarchy.
to:
'''3.''' Create a Representation of Your Data on the Graph.

Create new table occurrences on your relationship graph to represent the data you'd like to see in the hierarchy. (Don't worry about having [[multiple hierarchies]] at this point, you can come back to that later.) In our example we have Companies, Projects, and Tasks, and each of these is related to each other as you'd expect: Companies and Projects by CompanyID, then Projects and Tasks by Project ID. You may already have a section of your relationship graph which depicts this "natural" relationship between your tables, but you'll need a separate one for the hierarchy.
Changed lines 29-30 from:
'''4.''' Create a Second Version of this TOG. Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:
to:
'''4.''' Create a Second Version of this TOG.

Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:
Changed lines 35-36 from:
'''5.''' Pasting in Field Definitions. If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields on at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields 'DisplayContentsLevel1Calc, ...Level2Calc, etc can't be entered by hand yet: we'll tackle those in the next two steps.)
to:
'''5.''' Pasting in Field Definitions.

If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields on at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields 'DisplayContentsLevel1Calc, ...Level2Calc, etc can't be entered by hand yet: we'll tackle those in the next two steps.)
Changed lines 43-51 from:
'''6.'''
to:
'''6.''' Linking "Hierarchy Portal" to "HierarchyPortalLevel1", "...Level2", etc. 

Move to the relationship graph in your file and connect the TO  "Hierarchy Portal" to "HierarchyPortalLevel1". Link "Level1KeyCalc" in "Hierarchy Portal" to the primary key field in "HierarchyPortalLevel1": in our example that would be the CompanyID field.

Continue, linking "Hierarchy Portal" to "HierarchyPortalLevel2" using "Level2KeyCalc" in "Hierarchy Portal" to the primary key field in "HierarchyPortalLevel2": in our example that would be the ProjectID field. Continue in this way until you've linked each of the "HierarchyPortalLevel..." TOs to "HierarchyPortal".

<< image >>

August 17, 2008, at 01:00 AM by 76.28.195.40 -
Changed lines 27-31 from:
'''5.''' Pasting in Field Definitions. If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields on at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields, using the notes below as a guide.)

You'll need to make a couple of minor changes once you paste
the fields in to your file. Here is a list of the changes you'll need to make. (Note that if you see more errors than these you may have slightly different names for your "Hierarchy" and "HierarchyPortalLevel1" etc. table occurrences. If that is the case, delete the newly pasted fields, correct the names of your TOs and try again.)

-->
to:
'''5.''' Pasting in Field Definitions. If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields on at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields. Note that fields 'DisplayContentsLevel1Calc, ...Level2Calc, etc can't be entered by hand yet: we'll tackle those in the next two steps.)

Note that the fields DisplayContentsLevel1Calc, ...Level2Calc, etc. paste over commented out
(that is, they are surrounded with /* .... */). We'll fix those in the next two steps.

If you see more errors than these (i.e. more fields commented out) you may have slightly different
names for your "Hierarchy" and "HierarchyPortalLevel1" etc. table occurrences. If that is the case, delete the newly pasted fields, correct the names of your TOs and try again.

'''6.'''
August 17, 2008, at 12:56 AM by 76.28.195.40 -
Changed lines 25-31 from:
<< image >>
to:
<< image >>

'''5.''' Pasting in Field Definitions. If you're using FileMaker Advanced, copy all the fields from the Hierarchy table in SeedCode Hierarchy and paste them into the Hierarchy table in your file. (If you're not using Advanced you'll need to recreate the fields on at a time. If you're doing this one at a time, start with the regular fields first and then move to the calculation fields, using the notes below as a guide.)

You'll need to make a couple of minor changes once you paste the fields in to your file. Here is a list of the changes you'll need to make. (Note that if you see more errors than these you may have slightly different names for your "Hierarchy" and "HierarchyPortalLevel1" etc. table occurrences. If that is the case, delete the newly pasted fields, correct the names of your TOs and try again.)

--
>
August 17, 2008, at 12:51 AM by 76.28.195.40 -
Changed lines 7-10 from:
Moving SeedCode Hierarchy into your file is much easier if you have FileMaker Advanced, since it allows you to copy and paste field definitions and custom functions between files. You can integrate the hierarchy without Advanced, it is just a bit more work. So if you don't have advanced, consider getting a copy: you'll appreciate it. Otherwise, feel free to contact SeedCode, we can do this integration for you in just XXXXX.

!! Getting Started
to:
Moving SeedCode Hierarchy into your file is much easier if you have FileMaker Advanced, since it allows you to copy and paste field definitions between files. You can integrate the hierarchy without Advanced, it is just a bit more work. So if you don't have [[http://www.filemaker.com/products/fmpa/index.html | FileMaker Advanced]], consider getting a copy: you'll appreciate it. Otherwise, feel free to contact SeedCode, we can do this integration for you in just XXXXX.

!! Getting Started: The Relationship Graph in Your File
Changed lines 13-19 from:
'''2.''' Custom Functions. There are two custom functions used in SeedCode Hierarchy and you'll want to move them into your file before you get started. These functions are used in formatting the hierarchy as an outline, so if you don't need to do that you can skip this section. Also, if you're not using FileMaker Advanced you'll need to .

!! The Relationship Graph in Your File


'''3
.''' Create a New Table. Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them along on your relationship graph.
to:
'''2.''' Create a New Table. Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them along on your relationship graph.
Changed lines 17-18 from:
'''4.''' Create a Representation of Your Data on the Graph. Create new table occurrences on your relationship graph to represent the data you'd like to see in the hierarchy. (Don't worry about having [[multiple hierarchies]] at this point, you can come back to that later.) In our example we have Companies, Projects, and Tasks, and each of these is related to each other as you'd expect: Companies and Projects by CompanyID, then Projects and Tasks by Project ID. You may already have a section of your relationship graph which depicts this "natural" relationship between your tables, but you'll need a separate one for the hierarchy.
to:
'''3.''' Create a Representation of Your Data on the Graph. Create new table occurrences on your relationship graph to represent the data you'd like to see in the hierarchy. (Don't worry about having [[multiple hierarchies]] at this point, you can come back to that later.) In our example we have Companies, Projects, and Tasks, and each of these is related to each other as you'd expect: Companies and Projects by CompanyID, then Projects and Tasks by Project ID. You may already have a section of your relationship graph which depicts this "natural" relationship between your tables, but you'll need a separate one for the hierarchy.
Changed lines 23-24 from:
'''5.''' Create a Second Version of this TOG. Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:
to:
'''4.''' Create a Second Version of this TOG. Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:
August 17, 2008, at 12:33 AM by 76.28.195.40 -
Changed lines 5-6 from:
!! Getting Started: The Relationship Graph in Your File.
to:
!! About FileMaker Advanced

Moving SeedCode Hierarchy into your file is much easier if you have FileMaker Advanced, since it allows you to copy and paste field definitions and custom functions between files
. You can integrate the hierarchy without Advanced, it is just a bit more work. So if you don't have advanced, consider getting a copy: you'll appreciate it. Otherwise, feel free to contact SeedCode, we can do this integration for you in just XXXXX.

!! Getting Started

Changed lines 13-14 from:
'''2.''' Create a New Table. Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them along on your relationship graph.
to:
'''2.''' Custom Functions. There are two custom functions used in SeedCode Hierarchy and you'll want to move them into your file before you get started. These functions are used in formatting the hierarchy as an outline, so if you don't need to do that you can skip this section. Also, if you're not using FileMaker Advanced you'll need to .

!! The Relationship Graph in Your File


'''3
.''' Create a New Table. Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them along on your relationship graph.
Changed lines 22-23 from:
'''3.''' Create a Representation of Your Data on the Graph. Create new table occurrences on your relationship graph to represent the data you'd like to see in the hierarchy. (Don't worry about having [[multiple hierarchies]] at this point, you can come back to that later.) In our example we have Companies, Projects, and Tasks, and each of these is related to each other as you'd expect: Companies and Projects by CompanyID, then Projects and Tasks by Project ID. You may already have a section of your relationship graph which depicts this "natural" relationship between your tables, but you'll need a separate one for the hierarchy.
to:
'''4.''' Create a Representation of Your Data on the Graph. Create new table occurrences on your relationship graph to represent the data you'd like to see in the hierarchy. (Don't worry about having [[multiple hierarchies]] at this point, you can come back to that later.) In our example we have Companies, Projects, and Tasks, and each of these is related to each other as you'd expect: Companies and Projects by CompanyID, then Projects and Tasks by Project ID. You may already have a section of your relationship graph which depicts this "natural" relationship between your tables, but you'll need a separate one for the hierarchy.
Changed lines 28-29 from:
'''4.''' Create a Second Version of this TOG. Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:
to:
'''5.''' Create a Second Version of this TOG. Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:
August 17, 2008, at 12:25 AM by 76.28.195.40 -
Changed lines 5-6 from:
!! Getting Started
to:
!! Getting Started: The Relationship Graph in Your File.
Added lines 17-20:
<< image >>

'''4.''' Create a Second Version of this TOG. Now create a second version of this TOG in your graph. The table occurrences in this second group don't need to be related to each other but I usually begin by drag-copying the first group, renaming the TOs, and then deleting the relationships between them. The names of the TOs in this group will be similar to those in the first group, but instead of the word "Data", they'll use the word "Portal" so that the Companies TO (in our example) would be named "HierarchyPortalLevel1" (without the quotes), Projects would be "HierarchyPortalLevel2", etc. When you're done, this section of your relationship graph should look like this:

August 17, 2008, at 12:20 AM by 76.28.195.40 -
Changed lines 9-17 from:
'''2.'''
to:
'''2.''' Create a New Table. Create a new table in your file called "Hierarchy"; this doesn't have to have any fields associated with it yet, so just make the table and nothing else. A table occurrence (TO) for this will be added to your relationship graph. Create a second TO based on Hierarchy and name it "HierarchyPortal". You don't need to related these two to anything, just leave them along on your relationship graph.

<< image >>

'''3.''' Create a Representation of Your Data on the Graph. Create new table occurrences on your relationship graph to represent the data you'd like to see in the hierarchy. (Don't worry about having [[multiple hierarchies]] at this point, you can come back to that later.) In our example we have Companies, Projects, and Tasks, and each of these is related to each other as you'd expect: Companies and Projects by CompanyID, then Projects and Tasks by Project ID. You may already have a section of your relationship graph which depicts this "natural" relationship between your tables, but you'll need a separate one for the hierarchy.

So make a simple Table Occurrence Group (TOG) for use in the hierarchy and relate your version of Companies, Projects, and Tasks to each other as naturally as possible. Then, rename the table occurrences so that the top-level TO (Companies in our example) is named "HierarchyDataLevel1" (without the quotes), the next one down is "HierarchyDataLevel2", etc. You'll find a TOG like this in the relationship graph of SeedCode Hierarchy and make sure you match the TO names used there exactly.

<< image >>
August 17, 2008, at 12:09 AM by 76.28.195.40 -
Added lines 1-9:
!! Overview

SeedCode Hierarchy is made to be used with your own files: you can teach the hierarchy about our own tiered structures and see your records within the hierarchy. You'll actually add the hierarchy code to your file so that SeedCode Hierrachy.fp7 doesn't have to be part of your solution and can be something you use just for reference: the whole hierarchy will be ''in'' your file. The following instructions will  walk you through this step-by-step.

!! Getting Started

'''1.''' Backup your files. Really.

'''2.'''
(855) SEEDCODE
support@seedcode.com
Follow us: