@CSANDMS1,
On the differences error, did you define an Output data item names differences too? If so, that's the cause. Basically you have an Output variable with the same name as the internal var differences variable you defined in the code. If you refer back to my example, I used a capital "D" on the output data item. It makes a difference, no pun intended, because of case sensitivity.
​
For the first error, I'm not sure on that one. Would you post a screenshot of your Code Options page?
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
On the differences error, did you define an Output data item names differences too? If so, that's the cause. Basically you have an Output variable with the same name as the internal var differences variable you defined in the code. If you refer back to my example, I used a capital "D" on the output data item. It makes a difference, no pun intended, because of case sensitivity.
​For the first error, I'm not sure on that one. Would you post a screenshot of your Code Options page?
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
Original Message:
Sent: 03-10-2022 12:41From: Eric Wilson
Subject: Issue related Excel Data Comparison
@cs,
On the differences error, did you define an Output data item names differences too? If so, that's the cause. Basically you have an Output variable with the same name as the internal var differences variable you defined in the code. If you refer back to my example, I used a capital "D" on the output data item. It makes a difference, no pun intended, because of case sensitivity.
​For the first error, I'm not sure on that one. Would you post a screenshot of your Code Options page?
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
@cs,
The first, of the two, compile errors you have there is because you're defining an output variable in the Code1 stage, on the page Community Solution, called differences, but you're also defining an actual C# variable in the source code named differences.
​Notice, I've changed the Output parameter name to Differences with a capital 'D'. There are a million different ways you could change this to resolve the name conflict.
I'm thinking once you resolve that name conflict, it may resolve the second error too.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
The first, of the two, compile errors you have there is because you're defining an output variable in the Code1 stage, on the page Community Solution, called differences, but you're also defining an actual C# variable in the source code named differences.
​Notice, I've changed the Output parameter name to Differences with a capital 'D'. There are a million different ways you could change this to resolve the name conflict.
I'm thinking once you resolve that name conflict, it may resolve the second error too.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
Original Message:
Sent: 03-24-2022 22:59
From: Eric Wilson
Subject: Issue related Excel Data Comparison
@cs,
The first, of the two, compile errors you have there is because you're defining an output variable in the Code1 stage, on the page Community Solution, called differences, but you're also defining an actual C# variable in the source code named differences.
​Notice, I've changed the Output parameter name to Differences with a capital 'D'. There are a million different ways you could change this to resolve the name conflict.
I'm thinking once you resolve that name conflict, it may resolve the second error too.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
Sent: 03-24-2022 22:59
From: Eric Wilson
Subject: Issue related Excel Data Comparison
@cs,
The first, of the two, compile errors you have there is because you're defining an output variable in the Code1 stage, on the page Community Solution, called differences, but you're also defining an actual C# variable in the source code named differences.
​Notice, I've changed the Output parameter name to Differences with a capital 'D'. There are a million different ways you could change this to resolve the name conflict.
I'm thinking once you resolve that name conflict, it may resolve the second error too.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
@cs,
You're kill'n me. :face_with_tears_of_joy:
In your screenshot of the DLL's, you show the language has been set to Visual Basic. The example code I posted for you, is written in C#. The VBO you posted yesterday was also set to C#. So, somewhere along the line the language was changed. You need to change it back to C#, or, if you require VB for some other code stage you may be running, you'll have to convert the example code I gave you to VB.
​
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
You're kill'n me. :face_with_tears_of_joy:
In your screenshot of the DLL's, you show the language has been set to Visual Basic. The example code I posted for you, is written in C#. The VBO you posted yesterday was also set to C#. So, somewhere along the line the language was changed. You need to change it back to C#, or, if you require VB for some other code stage you may be running, you'll have to convert the example code I gave you to VB.
​Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
