Error message: string provided where a number is required.

Hi all,

I am trying to build an iterative macro for repayments on outstanding loan balances and I keep running into the following error when I run a workflow that contains the macro:

Tool 17 is a formula tool with the following argument:

where all three fields are a "double" type.

The tricky part is that when I simply run the macro, the process works as expected. But when I run the broader workflow, the error is thrown.

I have double checked and the data type in the macro is the same type as the data type in the workflow, but obviously I am just missing something. Can anyone point me in the right direction?

Thanks.

Error Message

Iterative Macro

Accepted answers

ImadZidan

Hello @JoeBarndollar ,

it is difficult guessing here without seeing the data in action.

Could it be that you have null values in ur data.

Can you try wrapping you if condition with tonumber.

So, it will look like If tonumber([Residual Loan/Repayment],3)<0 then ....

All comments

ImadZidan

Hello @JoeBarndollar ,

it is difficult guessing here without seeing the data in action.

Could it be that you have null values in ur data.

Can you try wrapping you if condition with tonumber.

So, it will look like If tonumber([Residual Loan/Repayment],3)<0 then ....

JoeBarndollar

It is possible that there could be nulls in later iterations of the macro.

I tried wrapping the fields in the formula tool as well. It results in the same error again. However, if I delete the negative sign in the formula, then the error changes to:

This references a filter tool further in the Macro which filters the "amount of loan" field based on the value being positive or negative.

Apologies, but I can't share the workflow. I would be happy to send any screenshots.

Thanks,

Joe

JoeBarndollar

Hi,

I followed the logic of wrapping my values with "tonumber" and that led me to delete and reinsert a few tools that referenced the "amount of loan" field (as these tools must have had a bug in them).

The macro works now.

Thanks for your help.

Quick Links

This months top contributors

LanisC 335

hhaigh1 280

erich_shiino 280

FláviaB 262

JORGE4900 235