| Q |
What is "Subset Insight" and when should I use it? |
| A |
An export doesn't just show that
a row was collected - it can also explain why: which association brought it in, and
the whole chain of rows back to the subject. This is invaluable when an
extraction model pulls in more rows than expected and you need to find
the association responsible (see also the "Why am I getting so
much data back?" question on the General
Questions FAQ page, and Step 4 of
the Tutorial).
|
| Q |
How do I enable it? |
| A |
There is nothing to turn on separately - it is available
automatically whenever the export uses the global tables working-table scope (the
default) in the Data Export
dialog.
|
| Q |
Can I inspect this while the export is still running, or only afterwards? |
| A |
Both. Rows already collected can be inspected while the collection
is still in progress, not just after it finishes - with one exception:
a run started with -transactional
keeps everything inside a single database transaction, so nothing is
visible until the whole run has committed.
|
| Q |
Where do I find this in the Progress dialog? |
| A |
A collapsible Subset Insight
Guide box lists every way to open the collected rows in the Data
Browser:
- Rows per Table:
double-click a table, or right-click it for Open Collected Rows in Data Browser -
only the rows collected for that table so far.
- Export tab (the progress
table): double-click or right-click a cell for Show Collected Rows - the chain of rows
leading from the subject down to it.
- Analysis tab:
right-click a row for Open in Data
Browser - the whole table, unfiltered.
- Once rows are open in the Data Browser itself: right-click any
row for Why is this Row in the
Subset? or Open Path to
Subject.
|
| Q |
What does "Open Path to Subject" show me? |
| A |
It opens the chain as a sequence of table browsers in the Data
Browser: one browser per step, from the subject down to the row you
selected, each showing the single row it was collected
through.
|
| Q |
What happens to this analysis data afterwards - is it left behind in my database? |
| A |
No. It is held only temporarily, in the same working tables the
export itself uses, and is discarded automatically once you close the
Progress window, start another run, or reconnect to the database -
whichever comes first. Nothing is left behind for you to clean
up.
|
