Why are there fewer nodes in my dataset than my source file? – Orgvue Knowledge Base

When loading data from the implementation hub, sometimes you will end up with less nodes than are in your source files. This would occur for two reasons:

Duplicates:
The implementation hub cannot load duplicate ID values to your Enterprise datasets. Therefore, if there are duplicate IDs in your source file, the node count in your dataset will be less than the source file.
To identify if this has happened to your dataset, check the following:

In the Implementation Hub go to Jobs > History
Then click on the Job Name link of the last data refresh to view the details
Review the number of nodes that have been loaded for each dataset type and if there were any duplicates.

If there were duplicates, the 'Nodes loaded' and 'Duplicates removed' should equal the 'Total records' i.e., the total records in your Source file.

A key call out for the links dataset is a link will not be created if FTE/allocation value used has any blanks. To check if this occured, you will need to check the number of blanks in your source file for the FTE/allocation. The number of blanks, along with the number of links created should equal the number of records in the source file.

Missing IDs:
A node cannot be created in Orgvue without an ID field.
To identify if this has happened to your dataset, check the following:

In the Implementation Hub go to Jobs > History
Then click on the Job Name link of the last data refresh to view the details
In your source file, identify the ID column. Check the number of blanks in this column. The number of blanks, along with the 'Nodes loaded' created should equal the number of records in the source file.