Bugs
Connector schema attribute settings are reflected to the adapter in a join transformation
Hi Gents,
Raising this in regards to an issue experienced recently at DCCEEW.
An adapter that is primarily used to provision out to a target system was modified with a join transform to include an additional attribute from another connector. This attribute happened to be the key field for the connector it was sourced from and naturally configured as a required field in the connector schema. After the join transform was applied the attribute was added to the adapter schema, but in addition the required field status was also reflected on the adapter.
As this was a mapped field, and not included in the attributes being exported through the adapter, this caused exports to fail with a schema validation error.
Attributes mapped via a join transform should not be set as required on the adapter schema.
Answer
Morning Richard,
Thanks for raising this. We already override the "key" and "readonly" properties on the schema mapping, so I'm assuming the "required" property was just overlooked.
We'll do some further validation to confirm and look to fix this one. Do you need a patch for 5.3, or are you happy with this being rolled into v6?
Afternoon Richard,
We've fixed this with UNIFYConnect v8.0.212346. Adapter fields now get mapped with no carry-over requirements from connector fields - "readonly", "key" and "required" are all set to false.
Customer support service by UserEcho
Afternoon Richard,
We've fixed this with UNIFYConnect v8.0.212346. Adapter fields now get mapped with no carry-over requirements from connector fields - "readonly", "key" and "required" are all set to false.