Customer HRIS often generate employee or position IDs that start with 0s. Orgvue can store these when the property is formatted as Text. However, this poses a risk when exporting and importing back into Orgvue.
For example,
If I had the following data In Orgvue:
Position ID | Title | Location | Manager ID |
001 | CEO | London | |
002 | CFO | Paris | 001 |
003 | COO | Paris | 001 |
I want to make a number of changes to my data, so I decide to make them in Excel and then Paste Merge the data back into Orgvue.
As soon as I export the data then Excel detects the data format. Therefore, the data looks like this:
Position ID | Title | Location | Manager ID |
1 | CEO | London | |
2 | CFO | Paris | 1 |
3 | COO | Paris | 1 |
This means that when I make my changes and paste merge the data back into Orgvue then Orgvue thinks that there are new positions and will treat the data as follows:
Position ID | Title | Location | Manager ID |
001 | CEO | London | |
002 | CFO | Paris | 001 |
003 | COO | Paris | 001 |
1 | CEO | London | |
2 | CFO | Paris | 1 |
3 | COO | Paris | 1 |
To stop this from happening then we recommend adding text in-front of your IDs and Parent IDs.
For example, instead of 001, user POS-001 or EMP-001. This formula is easy to create in Excel.
Alternatively, if you are loading data through the Implementation refresh then the Orgvue team will configure this so that IDs are updated automatically.
What if I am too late and I have already loaded my data?
If you have already loaded your data and are experiencing problems, then do not despair. Either raise a ticket with our Service Desk or speak to your Customer or Partner Success Manager to look at options.
Comments
0 comments
Please sign in to leave a comment.