What to do when encountering an error when an item with the same key has already been added or exist.
When configuring or running a Scribe solution, to Query or Update\Insert records for an Acoustic Campaign Contact Database, the GetLists API is submitted by the Silverpop Connector to retrieve the databases available for the next action in Scribe Online.
The main criteria for the databases being retrieved by the API are:
- Shared (not in private folders)
- Active (not archived)
The Response given to Scribe Online is a list of all the databases available.
If the API encounters duplicate database names, an error is displayed in Scribe Online.
- An item with the same key has already been added.
- Failure completing metadata request: An item with the same key has already been added.
Other symptoms displayed when editing mappings:
- No mappable fields exist on the chosen entity.
- Field is not found in Target Entity
Another related error that may occur during execution is
- Unable to retrieve lists with type database
All reflect the inability to get past the GetLists request and continue to the next steps for the map.
Resolving the problem
Finding the duplicate database names can be challenging if they were created by different users and exist in separate folders.
If many databases exist, it best to open an Acoustic Campaign support case and request a quick check of duplicate database names matching the criteria used by the API. Often the databases are created by different users and exist in different folders.
Once the duplicates are identified, the names can be changed, or unnecessary duplicates deleted.
Reset the metadata for the Silverpop Connection in Scribe Online, after the Acoustic Campaign database changes are complete, for the solution and map configurations to be updated.