Code stage and not initialized number/flag collection values
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-07-21 09:55 AM
Hi all,
does anybody know if there is a chance to correctly pass in a collection with not initialized number or flag values into a code stage?
It seems that all values will be converted to their .NET defaults e.g. a not-filled number becomes 0 and a not-filled flag becomes 'False'.
The reverse transfer (out of the code stage) works properly. Set a DataTable field to DBNull.Value appears as not-filled in BluePrism!
does anybody know if there is a chance to correctly pass in a collection with not initialized number or flag values into a code stage?
It seems that all values will be converted to their .NET defaults e.g. a not-filled number becomes 0 and a not-filled flag becomes 'False'.
The reverse transfer (out of the code stage) works properly. Set a DataTable field to DBNull.Value appears as not-filled in BluePrism!
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-07-21 02:49 PM
Hi @Tobias Arnold,
I've run a few tests around this. It seems that values will be initialized to their data type default as you observed.
Cheers,
Eric
I've run a few tests around this. It seems that values will be initialized to their data type default as you observed.
Cheers,
Eric
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-07-21 08:23 AM
Hi @EricWilson1,
Thanks for your feedback. I think I'll raise a ticket. It seems very odd to substitute NULL with default(typeof(T)).
Thanks,
Tobias
Thanks for your feedback. I think I'll raise a ticket. It seems very odd to substitute NULL with default(typeof(T)).
Thanks,
Tobias
