SeedCodeHierarchy

Troubleshooting

SeedCodeHierarchy.Troubleshooting History

Hide minor edits - Show changes to output

Changed lines 5-7 from:
Also, compare your graph to the screen shots in our [[integration]] instructions: make sure that "HierarchyPortal" is between "Hierarchy" and your "HierarchyPortalLevel..." table occurrences.

If
you're having trouble making new records in [[UsingExampleThree | Example Three]], make sure that you have your foreign key fields on each of the "HierarchyLevel__" layouts and that these fields are a) from the same table the layout is based on and , b) enterable in browse mode.
to:
Remember, all of the "HierarchyPortal..." relationships to your tables use the unique IDs of your tables (the primary keys). The only place you use something in addition to your primary keys is in the "HierarchyData..." relationships.

Also, compare your graph to the screen shots in our [[integration]] instructions: make sure that "HierarchyPortal" is between "Hierarchy" and your "HierarchyPortalLevel..." table occurrences.

If you're having trouble making new records in [[UsingExampleThree | Example Three]], make sure that you have your foreign key fields on each of the "HierarchyLevel__" layouts and that these fields are a) from the same table the layout is based on and , b) enterable in browse mode.
Changed lines 5-7 from:
Also, compare your graph to the screen shots in our [[integration]] instructions: make sure that "HierarchyPortal" is between "Hierarchy" and your "HierarchyPortalLevel..." table occurrences.
to:
Also, compare your graph to the screen shots in our [[integration]] instructions: make sure that "HierarchyPortal" is between "Hierarchy" and your "HierarchyPortalLevel..." table occurrences.

If you're having trouble making new records in [[UsingExampleThree | Example Three]], make sure that you have your foreign key fields on each of the "HierarchyLevel__" layouts and that these fields are a) from the same table the layout is based on and , b) enterable in browse mode
.
Changed lines 3-5 from:
The most common problem hooking the hierarchy up to your files is in getting the table occurrence (TO) names wrong. Make sure these are '''exactly''' the same as the names shown in steps 3 and 4 of our [[integration]] instructions. If you got them wrong, fix them, and then re-start the instructions from this point, re-pasting the field definitions, scripts, and layout objects so everything lines up.
to:
The most common problem hooking the hierarchy up to your files is in getting the table occurrence (TO) names wrong. Make sure these are '''exactly''' the same as the names shown in steps 3 and 4 of our [[integration]] instructions. If you got them wrong, fix them, and then re-start the instructions from this point, re-pasting the field definitions, scripts, and layout objects so everything lines up.

Also, compare your graph to the screen shots in our [[integration]] instructions: make sure that "HierarchyPortal" is between "Hierarchy" and your "HierarchyPortalLevel..." table occurrences
.
Changed line 3 from:
The most common problem hooking the hierarchy up to your files is in getting the table occurrence (TO) names wrong. Make sure these are '''exaclyt''' the same as the names shown in steps 3 and 4 of our [[integration]] instructions. If you got them wrong, fix them, and then re-start the instructions from this point, re-pasting the field definitions, scripts, and layout objects so everything lines up.
to:
The most common problem hooking the hierarchy up to your files is in getting the table occurrence (TO) names wrong. Make sure these are '''exactly''' the same as the names shown in steps 3 and 4 of our [[integration]] instructions. If you got them wrong, fix them, and then re-start the instructions from this point, re-pasting the field definitions, scripts, and layout objects so everything lines up.
Added lines 1-3:
!! What went wrong?

The most common problem hooking the hierarchy up to your files is in getting the table occurrence (TO) names wrong. Make sure these are '''exaclyt''' the same as the names shown in steps 3 and 4 of our [[integration]] instructions. If you got them wrong, fix them, and then re-start the instructions from this point, re-pasting the field definitions, scripts, and layout objects so everything lines up.
(855) SEEDCODE
support@seedcode.com
Follow us: