Could someone give me some idea on how to solve this?

On the publisher channel I am receiving an attribute value from the
application which is being used to generate another attribute value in
the vault. This other attribute does not exist in the application, so I
am receiving 4 values from the application and trying to pass 5 values
to the vault.

In one of the configurations I had this policy among the publisher
channel creation policies with a set destination attribute value. It
worked fine with an add. However, if I am receiving a modify on a
non-associated object which then gets converted to an add, the
synchronization errors out. The error is that this 5th attribute does
not exist in the application schema. I moved that policy around in the
publisher channel and got the same results.

How should I approach this synchronization?

celsolima's Profile:
View this thread: