27-06-21 03:53 PM
27-06-21 05:00 PM
28-06-21 12:54 AM
14-03-22 05:50 PM
15-03-22 09:13 AM
16-03-22 10:08 AM
31-03-22 11:22 AM
20-09-23 01:10 PM
Hi all,
in my own experience, there is a bug here in the MS Excel VBO code. I have just experienced the same frustrating experience during debugging that makes no sense. Jesper Hededam called it out right in my case. Whenever I step into an excel object it loses the connection with the excel workbook. To me I think this means when we run something from the process and instantiate an instance of the object, that instance is different from the one we step into when we then perform a step into function.
In my case I was opening a report with a formatted Today() date so i stepped into it to change it on the fly and got the 'given key not present in the dictionary but when I stepped over it it worked fine. I can replicate this behaviour ad-inifinitum. To me I understand this as a bug in how Blue Prism is creating objects in memory and then which one is being referenced based on the action you take of stepping over or stepping into it.
The inverse behaviour is also true, if you step in first and continue stepping in the error doesn't appear, it only appears for me when I stepped over each stage first and then stepped in when I tried to read worksheet as collection.
regards
Dexter