![]() |
| |||||||
Automation Anywhere Post messages and questions related to Automation Software here. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
|
I call stored procedures from my tasks and often send strings as input parameters into them. I was getting an error today and didn't know why... I just realized what it was. It appears that any variables that contain strings longer than 100 characters cause the task to fail when they are passed as parameters into stored procedures. There is no indication of what the problem is, the task just fails and it tells you there is a problem on the line that calls the stored procedure. This is similar to how the task fails when you have a comma in a string that you pass in as a parameter. Anyone know how can I pass a string longer than 100 characters into my sproc? It would help if AA gave some more detailed information about errors, especially when they are not obvious like these two. Thanks! Tyler |
| |||
|
Hello, In our latest release, version 5.5.2 the Run Stored Procedure command has no upper limit on the length of the Procedure name. You can download free trial version of Automation Anywhere 5.5.2 from our website: Automation Anywhere - The Automation Software. Automate & Schedule IT & Business processes easily. You can view the new enhancements and the bug fixes in the latest version at, Automation Anywhere Enterprise Version History - The Automation Software. Automate & Schedule Business & IT processes easily. |
| |||
|
Thanks for the replies guys! I just want to confirm that the fix in the new 5.5.2 version will solve my problem. My problem is not the length of the stored procedure name, it is the length of a parameter that is passed into the stored procedure. Has that been fixed as well? |
| |||
|
Hello, Yes, it is fixed. You can download Automation Anywhere 5.5.2 from our website: Automation Anywhere - The Automation Software. Automate & Schedule IT & Business processes easily. Hope that helps. |
![]() |
| Thread Tools | |
| Display Modes | |
| |