Hello,
I have added logic to MS Excel VBO to color a cell when the cell range input range is passed.
I just believe it is not a good practice because we will have to provide the MS Excel VBO to be imported in the production server if there is any new update released by Blueprism we will have to keep integrating it.. Is there any other way to handle this ?
Yes, make a copy of the VBO and put your amendments in the duplicate. Leave the original intact so you can import an newer version without overwriting your bespoke code. You can apply the same principle to all the utility objects.
Best practice is to never amend the standard package Blue Prism VBOs.
If you want to create a new action you should add it to a seperate object rather than amending a Blue Prism VBO.
To do this with Excel I have previously created a copy of the standard VBO with my new extended name and deleted all the actions except the ones related to lauch and attach. Then I added my new actions into it. When interfacing with Excel I might then have two objects connected to it.
I also tried saving the MS Excel VBO as a new Object and tried modifying it but i was unable to execute the stage that i need as it was failing in Check Handle stage.
So if any of you guys have added an extra stage could you please help me out with it as to how you went through it
You can use code stage for formatting the excel sheet any way you want. All you need is Interop DLL. Code stage will allow you to do formatting in few lines.
Thanks for your replies.
I actually did try saving it as a new one and then amending my actions to a new one. When i do this it always fails and i get an error ""The given key was not present in the dictionary"".
I am not sure why i am receiving this error i tired copying the MS Excel VBO from the previously existing one and added the new actions, also tried importing a new one and then added the new actions but still no go it just throws an error as mentioned above.
Any idea where i am going wrong