1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

Ticket #555 (closed defect: fixed)

Opened 12 months ago

Last modified 7 months ago

CSV import - issue with reconciliation keys

Reported by: romainq Owned by: romainq
Priority: major Milestone: 2.0
Component: Data Synchronization Version: 1.2.1
Keywords: Cc:

Description

To reproduce:

  • import objects having an attribute name
  • use the field 'name' as a reconcilation key
  • you will get an error:
    #Reconciliation Keys: friendlyname
    #exception 'CoreException' with message 'Wrong value for operator, found '=' while expecting a value in {}' in ....
    

The first thing that we notice here is the confusion that is made between the name and the friendlyname.

While allowing both localized names and attribute codes, itop should consider the attribute code as the one to take into account. The ambiguity should be reported anyhow.

Additionaly, to help in troubleshooting such an issue, when a label could not be identified, itop should report the whole list of allowed labels and the corresponding attribute.

More info: see related ticket #355

Quick Workaround


Modify the dictionnary and change the label of friendly names so that it get different from the label of names. This is in the file \dictionaries\[fr.]dictionary.itop.core.php

'Core:FriendlyName-Label' => 'Friendly Name',

Change History

Changed 12 months ago by romainq

See also documentation issue: #544. The documentation will be updated taking that comment into account.

Changed 7 months ago by romainq

  • status changed from new to closed
  • resolution set to fixed

Done in [2253]
The first attribute found with label "name" will be used. Therefore it will work 99% of the cases.
Moreover:

  • a warning is issued: Name is ambiguous: name and friendlyname were found. The attribute name will be used
  • the option no_localize allows to get back to a specification by the mean of internal codes (so called attribute codes), for which no ambuiguity is possible
Note: See TracTickets for help on using tickets.