When you load up the dataset, if OrgVue identifies any problems with the data, including building hierarchies, then it will provide a list of warnings/errors accessible via a red bar at the botton of the screen.
If you have potentially broken hierarchies imported into OrgVue, given the OrgVue warnings and guidance provided, it should be possible to fix the data structure by identifying problem nodes or relationships visually in OrgVue, or by filtering on metadata e.g. isOrphan, isDuplicate ...
... alternatively, as the warnings OrgVue generates relate to the original row IDs in Excel, once you have identified the ID that duplicates (in Excel) based on row number, you can use Excel 'find' to identify the duplications and correct as needed before saving in OrgVue i.e. reimport from Excel after correction
Approach: review import warnings
When you see the red lines (warnings) at the bottom of the page, you should open up the dialogue shown by expanding the message shown using the ^ symbol, this will give detail on the warnings encountered. Further details of common types are below.
Conceptually, as part of its import function, OrgVue accepts data provided that it is structured correctly and logical, but gives warnings about what is questionable about it e.g. duplicate IDs, missing parent IDs.
The extended messaging should be consulted and validated as the warnings do not assert that there is definitively an error e.g. successive references to the same ID will update exiting data in order within OrgVue:
Note any warning delivered will relate to the source data's row numbers e.g. Excel typically, not destination location in OrgVue dataset
A level of manual investigation would be required to validate if the warning is significant or not and there may be several iterations required here, including e.g.
- using OrgVue isDuplicate filters and/or
- using OrgVue isOrphan filters and/or
- Excel data validation tools in combination
If you no longer have the OrgVue import warnings visible i.e. because you have saved the OrgVue dataset, it may always be worthwhile re-uploading the data in question to a new dataset so you can review the warnings again only, then discard that dataset after warnings review.
Investigate: Circular reference at row [x] Please check the parent-child relationships
Circular references can be complex to investigate so we have provided this tool here to make the process more straightforward.
Please ensure all other warnings have been resolved before using the circular references resolution tool as it cannot work effectively if other import errors are still present in the data.
Investigate: Duplicate entry at row [x] Ensure the specific ids are different.
This would be possible if the same row data (i.e the unique person ID) were repeated and there were no data conflicts. If the person ID repeats, the rows will load sequentially and the latter row will overwrite the former one.
|ID Number||Manager ID||Full Name||Gender|
On that basis it would be possible that there is no duplicate within the data as seen in OrgVue, because OrgVue has 'smoothed' the data on load (Amber's manager will be set to Sarah), but the reported duplicate row in the OrgVue warning would refer to Excel.
The quickest way to investigate this would be to check in Excel using options Data -> Filter -> Advanced -> Unique records only in a new workbook
which would have the effect of "hiding" duplicate records, therefore you can investigate missing rows in the base spreadsheet from which you were loading into OrgVue.
For further information on why source data may contain duplication and how to manage this directly in the data source, see this article
Parent entry at row [x] does not exist. Please ensure all required fields are provided
The message here says, the parent ID being referenced does not exist in this dataset, although, in the circumstances you indicate, will not prevent the dataset loading but will likely mean you end up with orphans simply because the referenced parent does not exist.
The Parent entry at row .... will report rows where there is no parent ID on loading using the Tree by IDs option. Using the example below:
|ID Number||Manager ID||Full Name||Gender|
There will be a warning for Reece Harris, but this is correct because Reece is at the top of the hierarchy so has no parent: if however Molly White had no parent ID this would be significant, as Reece has already been identified as top of the hierarchy, so if Molly White had no parent ID too, this would need to be investigated.