Get Collection Fields incorrectly defines Date and Time fields as DateTime

blue_meanie — Fri, 30 Jul 2021 15:17:22 GMT

In Utility - Collection Manipulation, action Get Collection Fields is returning a DataType of DateTime for any fields formatted in the input collections as either Date, Time or DateTime.

Looking at the global code, there is a Function defined as GetBluePrismDataType, which uses a case statement to categorise the Data Type, based on the DotNetType value returned.

Is the issue with this global code, or is the DotNetType function actually flawed?

If anyone has any ideas of how this action/code stage could be 'fixed', I would be forever in your debt!

Thanks

UPDATE - I've just realised that there is some new steps in the Global Code in the latest packaged VBO version for V6.8, which does look like it was put in there to deal with the issue.... however, these new functions do not appear to be called anywhere in the Object! I've updated the Global Code in our Object, but it still doesn't work.

This makes me think that the issue was acknowledged, but perhaps hasn't been sorted?

Re: Get Collection Fields incorrectly defines Date and Time fields as DateTime

blue_meanie — Fri, 30 Jul 2021 16:32:19 GMT

Have 'solved' this with a logic bodge. It's not pretty, but it works!

Unfortunately won't work, if the input Collection is blank (will just return the data definition as it would have done previously), but i'm happy to live with that.

Re: Get Collection Fields incorrectly defines Date and Time fields as DateTime

krishna.kodimurali9 — Mon, 02 Aug 2021 11:48:54 GMT

Workaround is good, thanks for sharing

topic Re: Get Collection Fields incorrectly defines Date and Time fields as DateTime in Product Forum

Get Collection Fields incorrectly defines Date and Time fields as DateTime

Re: Get Collection Fields incorrectly defines Date and Time fields as DateTime

Re: Get Collection Fields incorrectly defines Date and Time fields as DateTime