#Couldn't convert 0.169760876645622 to number

1

Hi all,

I have a query to load data from Oracle db with formula and table is showing some values are could not get converted to number. Are there any limitation in easyMorph how many digits it supports after decimal point?
image

I am using version 4.3.1.5
Thanks.

2

Hi @bolud,

EasyMorph supports numbers with 28-29 significant digits. And NUMBER type in Oracle may have up to 38 significant digits.

The workaround here is to add something like ROUND("COLUMN", 20) to your formula.

3

Hi,

I’m using version 4.7.0.6, and I have that issue also. I’m using Oracle database and the data type is a FLOAT(126). On custom SQL I can use the workaround that you mentioned, by using round function. But since some users use the visual way, there is other way of fix it?

Thank you.

4

Hi @isabcabral and welcome to the Community!

You can extract the numeric value from the error message and convert it into a number using the method from the attached project. In this case, users can convert errors into numeric values.

convert-error.morph (2.5 KB)

image
image859×298 12.8 KB

5

Hi @dgudkov,

Thank you for your help, but I can’t open the project:

“An error has occured while opening the project: Object reference not set to an instance of an object.”

6

My EasyMorph version is 4.7.1. I tried to make the project work in 4.7.0 but apparently it didn’t happen.

I’ve updated my reply above with a project for v4.7.1 and added a screenshot. If you don’t have 4.7.1 installed, you should still be able to figure out the logic from the screenshot.

7

Hi @isabcabral,

Also, you can create an expression with the ROUND() function and then use that expression instead of a column to add conditions:

image
image1062×807 35.4 KB

1 Like
8

Hi Team -
I hate to re-open a topic but we just ran into this because no error was fired in the UI, when the error was found as noted in these screens.

2 Questions:

  1. Is it possible to easily stop a flow when an error like this occurs?
  2. is it possible to open up the limits to match the limit from database (*I know that is slippery because where do you draw the line)
9

Hi Adam,

The easiest way would be to use the "Halt on data type mismatch" action, which can stop a flow when an error is found in any column.

Also, all the export actions (except for the "Export dataset" action) should fail if the exported dataset contains an error.

That doesn't seem feasible.