Derek Knudsen
2005-09-01 23:40:02 UTC
I'm seeing a behavior that just doesn't seem right to me. We have a
PeopleSoft attribute being imported into MIIS, then exported out to AD and a
database. What I'm seeing is that if custom export rule extension for AD
fails, then the attribute doesn't get imported into the metaverse or exported
to the database. I can see it in the connector space for PeopleSoft as the
new value but it doesn't get set in the metaverse. Is this expected
behavior? Seems very counterintuitive that a failed export to one system
could prevent it from exporting to another. As an FYI, the error was a
AttributeNotDefinedAsSourceException, something we quickly fixed so
everything now works. Just found this behavior interesting.
PeopleSoft attribute being imported into MIIS, then exported out to AD and a
database. What I'm seeing is that if custom export rule extension for AD
fails, then the attribute doesn't get imported into the metaverse or exported
to the database. I can see it in the connector space for PeopleSoft as the
new value but it doesn't get set in the metaverse. Is this expected
behavior? Seems very counterintuitive that a failed export to one system
could prevent it from exporting to another. As an FYI, the error was a
AttributeNotDefinedAsSourceException, something we quickly fixed so
everything now works. Just found this behavior interesting.