Blue Prism reads flag as True when its False
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-07-22 02:28 PM
I have a collection (Item Data) that has a flag field. When I reference this field as part of an input to a business object the value is being read as True even when set to False. Is this a bug? I'm using Blue Prism v7

Part of me thinks it must be user error but I've checked everything I can think of and recreated the references and its still reading incorrectly
------------------------------
Ed Bailey
Service Management Analyst
Bupa Ltd
Europe/London
------------------------------
Part of me thinks it must be user error but I've checked everything I can think of and recreated the references and its still reading incorrectly
------------------------------
Ed Bailey
Service Management Analyst
Bupa Ltd
Europe/London
------------------------------
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-07-22 09:28 PM
Hi @EdBailey.
Does it read the field incorrectly when you actually run the process in debug or from Control Room? I don't think this is a bug. This is just the way the Evaluate Expression feature works when you're in design mode. In other words, if you're using Evaluate Expression during design, Blue Prism has no idea what record it's supposed to be looking at in the Collection. Now, if you see the same behavior while stepping through the process in debug, then it would be a bug.
Does that make sense?
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
Does it read the field incorrectly when you actually run the process in debug or from Control Room? I don't think this is a bug. This is just the way the Evaluate Expression feature works when you're in design mode. In other words, if you're using Evaluate Expression during design, Blue Prism has no idea what record it's supposed to be looking at in the Collection. Now, if you see the same behavior while stepping through the process in debug, then it would be a bug.
Does that make sense?
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-07-22 08:18 AM
Hi Eric
Yes that makes sense, thanks. Unfortunately it does read the field incorrectly as it passes the true value into a business object that then enters the wrong value into the application I am automating. This only came to light as part of UAT when I started running real test cases through my process.
------------------------------
Ed Bailey
Service Management Analyst
Bupa Ltd
Europe/London
------------------------------
Yes that makes sense, thanks. Unfortunately it does read the field incorrectly as it passes the true value into a business object that then enters the wrong value into the application I am automating. This only came to light as part of UAT when I started running real test cases through my process.
------------------------------
Ed Bailey
Service Management Analyst
Bupa Ltd
Europe/London
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-07-22 09:12 AM
Ah, actually its not passing the incorrect value into the business object (at least not today anyway). There is a different issue in the business object that's causing the incorrect value to be entered.
------------------------------
Ed Bailey
Service Management Analyst
Bupa Ltd
Europe/London
------------------------------
------------------------------
Ed Bailey
Service Management Analyst
Bupa Ltd
Europe/London
------------------------------
