- UNIFYBroker Forum
-
Questions
Adapter Error: DN Component, Argument Out of Range Exception
I have an adapter that is a position type that has a field for the ReportsTo position. I'm generating a DN on this field. I've got bad data here so it wouldn't be able to resolve the DN. My question is, should this prevent the entire adapter from loading in changes. Right now I've got 19 changes and 0 entities and this error being thrown. Does the bad DN reference prevent the whole thing from loading?
This is the error I'm getting:
Answer
Also, how does the DN Generator handle null values. If there's nothing in the field that a DN is being generated from, what should happen?
Hey Daniel,
In the case where you're using a field as the DN template for the adapter, currently that will stop all changes from being loaded into the adapter. We're currently making some improvements in this area to allow other changes to process - but it is correct that a missing value on the DN template will result in an error. Because the DN template is used to expose the data over the LDAP gateway to downstream systems, you can't have an empty DN.
In the case of bad data, it is recommended to use a field that always exists as the DN template. If this isn't available in the source data, you can use the @IdbID field which relates to the internal ID of that entity.
For the DN generator in the adapter transformations, there's an option to Skip Missing which will stop the adapter from attempting to generate a DN where a value for that field is missing. This only works when you're attempting to generate reference attributes through the transformation, this does not apply to the DN template field on the adapter.
Thanks, I don't think I explained properly. It's not the DN template of the adapter I'm talking about here, it's just a generate DN adapter transformation. So I can tick 'Skip Missing' for when the value may be blank. What if the generated DN doesn't exist in the target connector ie a reference to nothing. I think that's what's causing my problem and preventing the entire Adapter from loading.
Actually looking at my data, it's so bad, not one of the references would resolve so the error may or may not be stopping the whole connector or just each bad entry.
It'll stop reflection because of the nature of the way it's currently calculated and the requirement that the changes are in order. As Matthew mentioned we are exploring ways to improve this process. For now you'll need to fix the transformation configuration so that it does not error out. Regarding the generated reference, UNIFYBroker does not do reference checking, as it's assumed that this is done by the identity management platform.
Customer support service by UserEcho
It'll stop reflection because of the nature of the way it's currently calculated and the requirement that the changes are in order. As Matthew mentioned we are exploring ways to improve this process. For now you'll need to fix the transformation configuration so that it does not error out. Regarding the generated reference, UNIFYBroker does not do reference checking, as it's assumed that this is done by the identity management platform.