[SEO Utils] Item has already been added. Key in dictionary in SEO Utils

Forge Component
Published on 2019-03-28 by Miguel Seabra Melo
4 votes
Published on 2019-03-28 by Miguel Seabra Melo

I have created an application which uses SEOUtils extension GetScreenURL action to get the ScreenURL so that I reads the data configured in the SEO URLs configuration. However every time after the application is publish, when two users try to access the page first time, for one user the page gets loaded and the other gets an error saying "Item has already been added. Key in dictionary"

Below is the error

User: (516)
Session Id:XXXXXXX
Module:Extension metho
Message:Item has already been added. Key in dictionary: 'ConcurrencyIssue'  Key being added: 'ConcurrencyIssue'
Environment Information
Stack:Item has already been added. Key in dictionary: 'ConcurrencyIssue'  Key being added: 'ConcurrencyIssue'
   at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
   at OutSystems.NssSEOUtils.CssSEOUtils.GetEspaceId(String name)
   at OutSystems.NssSEOUtils.CssSEOUtils.MssGetScreenURL(String ssScreenName, String sseSpaceName, String ssFirstParameterName, String ssFirstParameterValue, String ssSecondParameterName, String ssSecondParameterValue, String ssThirdParameterName, String ssThirdParameterValue, String ssFourthParameterName, String ssFourthParameterValue, String ssFifthParameterName, String ssFifthParameterValue, String& ssURL)
   at ssConcurrencyIssue.RssExtensionSEOUtils.MssGetScreenURL(HeContext heContext, String inParamScreenName, String inParameSpaceName, String inParamFirstParameterName, String inParamFirstParameterValue, String inParamSecondParameterName, String inParamSecondParameterValue, String inParamThirdParameterName, String inParamThirdParameterValue, String inParamFourthParameterName, String inParamFourthParameterValue, String inParamFifthParameterName, String inParamFifthParameterValue, String& outParamURL)

Tagging Miguel SeabraMelo who created this component. Any help in here is very much appreciated.

Hi Aneesh,

What version of the component are you using? If using 1.2.0 please go back to Version 1.1.1 as there were problems detected with 1.2