• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 16 subscribers
  • Views 7722 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

User Names field mapping in quest tool

siva pemmasani
over 5 years ago

I added Names field in quest tool from lotus note and migrated it but still it is showing as CN name in SP as well

why it did not convert as an email.

In user mapping everything has done like below. still same value is coming to SP as it is in LN.

  • 0 over 5 years ago

    Hello, the user translation works only for fields that are of type "User" in both the Notes source and the SharePoint target.
    If you are seeing the CN name in SharePoint, it is very likely that the target field is a text field.

  • 0 over 5 years ago in reply to Peter.Mendelsohn

    it is name field actually , when I change it from string to User then if I try to see it in preview tab I am getting prompt that illegal option with column

    second one is if I make target type as user in sharepoint tab then after migration field value is system.object[]

    can you help me on this .

  • 0 over 5 years ago in reply to siva pemmasani

    It is hard to find the exact reason without more information.
    I have tested this in my lab: The source field can remain as "String", but the target field needs to be of type "User", or no user mapping occurs.

    A couple of things to check:
    - Have you looked at the logs? If the user mapping fails (which a target value of "system.object[]" pretty much implies), there should be something in the logs.
    - Is the account configured in MNSP to connect to SharePoint a Site Collection Administrator in the SharePoint target?
    - Have you tested the "Validate in SharePoint" button in the User mapping test (your screenshot above)?
    - Have you tried selecting the "Preserve created/modified identities" option on the mappings tab? This is the easiest way to check if the user mapping works.
    - While it should not be necessary, setting the "Input translation" to "Canonical" in the user mapping options does not hurt.

  • 0 over 5 years ago in reply to Peter.Mendelsohn

    Hi Peter,

    Thanks a lot for your response.

    I have attached here few screen shots for your reference.

    I attached screen print with log and with other details, I selected in SharePoint tab as an User. even though I got same error.

    2. I enabled options Preserve created and modified identifies and dates. here user email is coming up successfully. as I mentioned his name in default user name. you can see it in first screen shot

    3. It is a name field in Notes and I selected as string. user name has listed in domino address book. 

    4. I tried and validated user name in SharePoint and it was tested successfully. 

    5. Input translation I left as blank

    Please let me know if you require any more details.

  • +1 over 5 years ago in reply to siva pemmasani

    A successfull mapping will have a series of corresponding log entries.
    Here is an example:

    "Context:       Map User
    Message:       Map Notes user 'CN=Kimberly Piper/O=QDemo' to Windows user 'dellsoftware\kpiper' (NOT CACHED)

    Context:       Map User
    Message:       Found Windows Principal from name 'dellsoftware\kpiper' with email='', display name='Kimberly Piper', type='User'

    Context:       Map User
    Message:       Creating new Site Collection User 'Kimberly Piper' with Windows login 'i:0#.w|dellsoftware\kpiper' and Email ''

    Context:       Map User
    Message:       Created Site Collection User number '8' with login='i:0#.w|dellsoftware\kpiper', name='Kimberly Piper', email=''"

    Please check if these are present.