In the Export Precedence section of About Attribute Flow Precedence, the reason for my Skipped: not precedent is clearly described. However, I am still at a loss as to how to make FIM do what I want. How might I set up FIM to accommodate the following situation?
An HR system contributes employees to the metaverse, while contractors are manually entered into the FIM Portal. In the MV, the employeeType attribute needs to be populated. employeeType also needs to flow back to the FIM Portal for both contractors and employees, so MPRs/Sets/Workflows can be applied.
The HR sync rule contributes "Employee", while the FIM Portal contributes "Contractor". The MV has to flow back to the FIM Portal to update employees. If HR is precedent, "Contractor" never flows to the MV. If the Portal is precedent, "Employee" flows from HR to the MV to the Portal at projection, but then the Portal becomes precedent and a hired contractor cannot be updated when HR joins later.
It seems like there is no solution to this. I hope I am somehow misunderstanding. Any help would be appreciated.
Thanks in advance.