I am currently utilizing the community license, and the versions consistently update automatically.
I am encountering problems with the Assign and Input dialog box activities, including the “Object reference” error, as illustrated in the attached screenshot.
If we revert to the lowest version, 22 something, it functions properly, so I seek to comprehend the rationale behind upgrading to the new version when it does not support working activities.
There is no benefit in upgrading the version; it should enhance productivity rather than diminish it.
Hi @Mahesh_Kumar_Thotla , what version of Studio are you using where you’re encountering the issue? And how is the dictStrDetails variable initialized in the Data Manager or in the workflow? Would you be able to share the project by any chance?
The studio version 2026.0.189
I have attached the Xaml file as well, i dont think issues with actvities
seems issues with the package version only Main.xaml (22.4 KB)
Just to exclude the obvious ‘have you tried turning it off and on again’ causes:
In your screenshot, the error indicates a null-object. Are you sure the dictionary that is targeted is initialized in an earlier stage?
Assign: dictstrDetails = New Dictionary(of String, String)
And, is this dictionary in scope of your current sequence?
Since this would produce the same erorr if forgotten.Maybe the new version is stricter concerning scope of dictionaries compared to older versions?
Thank you, @Mahesh_Kumar_Thotla ,for sharing the project. I can see the dictionary variable dictStrDetails is not initialized in the workflow or in the Data Manager. By setting the default value to new Dictionary(of String, String), I was able to run it successfully.
I wasn’t able to run it successfully when changing the System package version, was this able to run successfully under a different setup?
Hi @Mahesh_Kumar_Thotla , just to double check here, the variable that is initialized in the Data Manager seems to be dictStrData while the assign references dictStrDetails. Did you also initialize dictStrDetails?
@Mahesh_Kumar_Thotla We can confirm that this is an issue in System 26.2.x version. We will soon release a patch to the System activities to fix this issue.
