No type validation on the constant transformation
Matthew Clark 10 years ago • updated by anonymous 7 years ago • 5
The Constant transformation has a feature to enter the type of value used for the constant. The default type is a Guid type field, and I am allowed to enter anything I want for its value. I am able to start an adapter with a constant value therefore populating a Guid field "newguid" with the string value "something". I was also able to do this with a date field. Depending on the type of field that gets mapped in FIM, I'm not entirely sure what would happen on an attempt to import this field - I imagine it would result in every entry failing with unexpected data, or possibly when committing the value to the adapter context.
Customer support service by UserEcho
The result is the following when you finally set up the MA and run an import:
This also halted the entire import process - it was not just an error on a per object basis
"Halted entire process" because the transformation factory couldn't be created. This is the correct behaviour. As for validation, exception description needs to be improved obviously; on the UI side, this is a little tricky to do on the client side, you could do it potentially pretty easily on the server side (validation errors).
Matthew Clark, I have updated the constant transformation to validate. Please let me know if you have any issues with it.
Confirmed or migrated to VSO.