Conversion script in DataImport OneIM 8

Hello!

I'm struggling with a "Conversion script" in DataImport tool (One Identity 8.1.4). I was searching for an example in documentations, but no luck...It only says that "$" and a "Value" keys should be used (like $0$ to access to the first column of the CSV file).But I still need an example to set a proper conversion code.

Also, when I'm starting some VB code in the "Conversion script", I get a message "Namespace member declaration expected".

Any ideas?

Best regards,

Top Replies

Markus Weiss-Ehlers over 3 years ago +1 verified

A proper sample would be:

Dim x As String = "0"
Select Case $4$.ToLower
    Case "hoch"
        x = "0,75"
    Case "mittel"
        x = "0,5"
    Case "gering"
        x = "0,25"
End Select
Value = CDbl…

Parents

+1 Markus Weiss-Ehlers over 3 years ago

A proper sample would be:

Dim x As String = "0"
Select Case $4$.ToLower
    Case "hoch"
        x = "0,75"
    Case "mittel"
        x = "0,5"
    Case "gering"
        x = "0,25"
End Select
Value = CDbl(x)

0 Anton Akimov over 3 years ago in reply to Markus Weiss-Ehlers

Thanks a lot Markus, it works perfectly!

A little question: our customer needs to import departments, users, etc. According to my understanding, the DataImport tool is a best choice to bring this type of data into OneIM without thinking of workflows, target schemas etc. I know that Synchronization Editor could also be used for that, but it seems to be much more powerfull but also may be more complex to maintain for this use case. Am I mistaken?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

0 Anton Akimov over 3 years ago in reply to Markus Weiss-Ehlers

Thanks a lot Markus, it works perfectly!

A little question: our customer needs to import departments, users, etc. According to my understanding, the DataImport tool is a best choice to bring this type of data into OneIM without thinking of workflows, target schemas etc. I know that Synchronization Editor could also be used for that, but it seems to be much more powerfull but also may be more complex to maintain for this use case. Am I mistaken?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

0 Markus Weiss-Ehlers over 3 years ago in reply to Anton Akimov

I think your summary is on point.

As an addition, if the import should be done on a regular base (sync) it makes sense to use the synchronization editor and the CSV connector to make use of the central logging scheme.
Cancel
Up 0 Down

Reply

Verify Answer

Reject Answer

Cancel