You’re offline. This is a read only version of the page.
Announcements
I'm getting an error message when running a map in SmartConnect:
"An item with the same key has already been added"
It's a simple map only pushing GL data but because we're only "test driving" SmartConnect we don't have any support just yet with eOne. Since this is just testing the software in Fabrikam I executed my map about 8 times (getting errors I had to sort through), but can't figure out this error?
Has anyone seen this before and can point me in the right direction for resolution?
Thanks,
Sean
*This post is locked for comments
Thank you Sean for that logical tip. I was going nuts over the duplicate entries until I found your posting here. Thank you very much for sharing how you solved that issue.
Hi Sandip -
No, this isn't eConnect but eOne's SmartConnect.
I was able to figure out my problem though, it seems (logically thinking through the process) SmartConnect has a sequence order. I mistakingly had the Add Distributions map go first instead of the create journal and once I flipped these two around it worked like a champion. I agree Richard, SmartConnect is a GREAT tool for GP admins who aren't familiar with eConnect.
Are we talking here about eConnect? If yes can you check event viewer log for eConnect?
Thanks
Sandip
Thanks for replying Richard - I appreciate the help!
I took what you said and did some investigative work. Prior to this previous run, my next journal entry number should have been 3479 so I did a search in the GL10000, GL20000 and GL30000 tables for this particular JE number and didn't see any (remember of course this is Fabrikam). For this particular map, I'm grouping by currency (our company uses Multicurrency) which there is only three and I have a GP Rolling Column setup for the Journal Entry number (which I found from eOne's knowledgebase). In following the kb article on their site, I assumed it would pull the next JE number from the GL setup in GP. So when I executed the map again, it took the next three journal entry numbers (next JE number is 3482) but then failed with the same message.
Any other thoughts on this?
What the message is saying is that the map is trying to push into the tables a transaction with the same journal number as an existing transaction (assuming you are loading transactions into GL) If you are loading the COA table, then you have a duplicate account index or account number.
Smart Connect is a GREAT tool and it will work for you once you learn how to use it. They have a great support team.
#1
André Arnaud de Cal...
293,311
Super User 2025 Season 1
#2
Martin Dráb
232,183
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
