0
Not a bug

Time Offset Flag Transformation throws error when no data present

Matthew Woolnough 4 years ago in UNIFYBroker/Microsoft Identity Manager updated by anonymous 4 years ago 6

The UI is displaying "Specified argument was out of the range of valid values. Parameter name: key"  after configuring a Time Offset Flag Transformation.   Looking at the data, there is nothing currently in the column, I suspect this might be causing the error. 

There are two configured transformations:

<adapter name="TimeOffsetFlag" key="e761c890-313b-4b88-bfcf-272595dcf784">
  <Extended offset="-P15DT10H" sourceColumn="DateCommenced" destinationColumn="EmployeeStarted" LesserValue="True" EqualValue="True" GreaterValue="False" NullValue="False" adjustForLocal="false" xmlns="" />
</adapter>
<adapter name="TimeOffsetFlag" key="00eaab5c-89e9-41b4-9728-e7b342d07db8">
  <Extended offset="PT10H" sourceColumn="DateTerminated" destinationColumn="EmployeeTerminated" LesserValue="False" EqualValue="True" GreaterValue="False" NullValue="True" adjustForLocal="false" xmlns="" />
</adapter>

The first one foes not throw an error. The second one does.



Affected Versions:
Fixed by Version:

Answer

Answer
Under review

Hi Matt,

Where is the UI displaying this error? Is it under the Transformations section, between a heading Time Offset Flag and its corresponding description? Please ensure that you don't have duplicate column names in your adapter, i.e. that there isn't already a column named DateTerminated. If there is, either rename the existing column or change the Target for the Time Offset Flag Transformation.

Answer
Under review

Hi Matt,

Where is the UI displaying this error? Is it under the Transformations section, between a heading Time Offset Flag and its corresponding description? Please ensure that you don't have duplicate column names in your adapter, i.e. that there isn't already a column named DateTerminated. If there is, either rename the existing column or change the Target for the Time Offset Flag Transformation.

There was an existing constant of the same name.  I've removed it and the error has gone. 

The error message does not provide helpful information IMO. 

Not a bug

Hi Matt,

Glad to hear the issue has been resolved, and thanks again for the feedback on the user experience.

Do I need to open another issue to suggest an enhancement, or are you guys on top of that?

We have an internal backlog item to improve user-facing error reporting, and I've made a note of this instance there.