OK, further fixes. Sorted the map container in $DisplayName order. Link types instituted. Edict now populating user attributes correctly. However $Name(ID-designator) fails to work if ID-designator.
To my understanding this is a bug as designators can be single or lists. Too much to fix and might need app level fix to complete this ask.
Even then, looking at export, the export is more complex as Stories/Studies can be one or more items and the table should have every (unique) combo of those o a separate line. Again this might need an extension to action code to handle.
Done for today, hereās the current file to play with. New typed links are visible but unlabelled - my terminology before was off. If you untick visible for a link type it hides both line and label; ālabeledā is the box youāre really after.
Looking at the XLS supplied, Iām assuming each _concept, has onemodel and one metaphor but Nstudy and Nstory items.
So, on export we need to loop through to give an output row of per unique (?) study:story combo. I can do all combos with nested links but that will give an entry for A:B and B:A as opposed to a single row for them both as I think A:B == B:A. True?
Yes, each concept has one model and one metaphor and N study and story items.
For the export, the numbers are so relatively low that double entries are not going to cause me that much work to clean up. The export would occur once, letās say, and with 15 concepts and, say, 2-3 studies and stories per concept, itās not much to go through and delete rows. A few minutes work.
Thanks. Actually, the problem Iām hitting is doing all the duplicate lines. Per row, weāve two multi-value columns, each unique pairing of which of which demands the row be duplicated.
If we just concatenated individual values (pre column), i.e. if 3 story sources we out put then as one dell item, it would be a lot easier.
The ## markers in some cells show where 've concatenated stories or studies. I tried adding vertical tab characters (Chr 10) but I donāt think Tinderbox uses the \v escape code. Still the hashes can easily be swapped out in the XLS file (or CSV, etc. when initially imported.
Sorry - v busy weekend so no time to annotate files. The Export agent is doing the main business, via a pair of templates. I forgot to set the export filename and file extension - use the HTML Inspector for that. For the sample in the Excel file I simply copied/pasted from the agentās Text pane HTML sub-pane.
FWIW, I first tried doing the export using action code variables in the code (var) but hit issues. So, Iām using to extra last attributes $MyListA and $MyListB as well as the built-in $MyString during export. The code voids all three at the end of the loop so we donāt end up storing unneeded data.