Skip to main content
SharePoint

Return to Answer

replaced http://sharepoint.stackexchange.com/ with https://sharepoint.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

It's SharePoint's CAML queries' way of working with calculated fields. This problem is described in https://deannaschneider.wordpress.com/2012/07/06/associated-calculated-columns-in-reusable-workflows-sp2010/ and "float;#22.0000000000000" Number Returned From CAML Query"float;#22.0000000000000" Number Returned From CAML Query

The straightforward workaround is to re-implement same calculations in the workflow once again.

Or you can create a workflow variable tempVar and set it's value to CurrentItem:No. of Days (as string), then use some Utility actions to get that 22 out of the string. Something like Extract Substring of String from Index with Length with args of tempVar, 7 and (the position of . char minus 7) will work. To find the position of ., use Find Substring in String. This will cut out 22 (basically, all chars between # and .) and put it in tempVar, so you can use it in emails.

It's SharePoint's CAML queries' way of working with calculated fields. This problem is described in https://deannaschneider.wordpress.com/2012/07/06/associated-calculated-columns-in-reusable-workflows-sp2010/ and "float;#22.0000000000000" Number Returned From CAML Query

The straightforward workaround is to re-implement same calculations in the workflow once again.

Or you can create a workflow variable tempVar and set it's value to CurrentItem:No. of Days (as string), then use some Utility actions to get that 22 out of the string. Something like Extract Substring of String from Index with Length with args of tempVar, 7 and (the position of . char minus 7) will work. To find the position of ., use Find Substring in String. This will cut out 22 (basically, all chars between # and .) and put it in tempVar, so you can use it in emails.

It's SharePoint's CAML queries' way of working with calculated fields. This problem is described in https://deannaschneider.wordpress.com/2012/07/06/associated-calculated-columns-in-reusable-workflows-sp2010/ and "float;#22.0000000000000" Number Returned From CAML Query

The straightforward workaround is to re-implement same calculations in the workflow once again.

Or you can create a workflow variable tempVar and set it's value to CurrentItem:No. of Days (as string), then use some Utility actions to get that 22 out of the string. Something like Extract Substring of String from Index with Length with args of tempVar, 7 and (the position of . char minus 7) will work. To find the position of ., use Find Substring in String. This will cut out 22 (basically, all chars between # and .) and put it in tempVar, so you can use it in emails.

Source Link
Aziz Kabyshev
Aziz Kabyshev
  • 1.6k
  • 11
  • 17

It's SharePoint's CAML queries' way of working with calculated fields. This problem is described in https://deannaschneider.wordpress.com/2012/07/06/associated-calculated-columns-in-reusable-workflows-sp2010/ and "float;#22.0000000000000" Number Returned From CAML Query

The straightforward workaround is to re-implement same calculations in the workflow once again.

Or you can create a workflow variable tempVar and set it's value to CurrentItem:No. of Days (as string), then use some Utility actions to get that 22 out of the string. Something like Extract Substring of String from Index with Length with args of tempVar, 7 and (the position of . char minus 7) will work. To find the position of ., use Find Substring in String. This will cut out 22 (basically, all chars between # and .) and put it in tempVar, so you can use it in emails.