Perform changes in the Positions by import when they are already used in Job Info

[adriangalisteo]

Hi Team,

The client sent me their position template to be uploaded and then we uploaded job info.

Now they say that they have to change the template because the position data was not correct.

If i try to full purge positions now, the system tells me that i cannot because X employees have the position in use. So it would force me to delete job info before which is a hard task and time consuming.

Also once we uploaded job info, it generated registers in the Positions so even if i recharge incremental load the file that client gave me corrected, it would only change the registers that have 01/01/1900 as a date, the ones before would continue the same.

How do you deal with this situations? My concern here is to find a faster way to make those changes in the positions without having to affect job info event though these positions are in Job Info already.

Regards

[Alina]

Hello, agali ,

As I understood, you need to delete the wrong records on positions.

You can delete all the records for an MDF object such as instances and entities using Delete operator in imports.

Just add Delete operator in the root template for the record that you want to delete from the instance.

The record is deleted during the incremental import.

I hope it helps.

Kind regards,

Alina

[nlgro023]

With such a change there's no easy way out and it depends on the volume of job info / position records on what approach will be most suitable. As you refer to a full purge for positions, potentially it's also worth the go (maybe with the sync column) to go for an incremental load instead so that both job and position info are updated (although you'd be accepting that there are job info records with incorrect info).

The cleanest way may in fact be taking an export of positions and job info (where job info would be taken via the person and employment export dimension via table reports) and using that to delete a reimport unfortunately. This doesn't have to take too long to be honest as you can add the delete / delimit (first job info, then positions) although it could be that you need to perform a look-up to match all the right records. You could potentially make some imports easier by using business rules / making fields non-mandatory, but that all depends on the volume/data etc.

If you are ok with "pollution" in the job info (as old positions with wrong data) may have affected the job info, then you could just choose to make new positions, import those and tie them to the job info records with a higher sequence.

In terms of mass transactions you could of course use integration center or mass data management for positions, but I doubt this use cases fits either of those.