Unparseable number error when creating a new change

frappe · ‎07-08-2016

Hi

Anyone know why I might be getting this message when creating a new Normal change? I don't believe this showed up in my dev instance until I created a risk assessment (which works beautifully). Is there some other rule enabled something out of box that's not happy? PS: It only shows up when creating a change before it's saved, once it's saved the error goes away. I want to demo but this is the first thing users will see so need to get rid of this error. Thanks

Chuck Tomasi · ‎07-08-2016

Hi Kristin,

Check the dictionary's default value for that field. It might have a - in it.

Right click the field label
Choose Configure Dictionary
Check the Default Value section, Default value field
Update if necessary

Other places to look, a business rule on that table that only runs on INSERT.

Click the form menu
Choose Configure> Business Rule
Filter on scripts where Insert | is | true AND Update | is | false AND Script | contains | risk
See if any of them set the value to -
Update if necessary

A choice list value that has - in it.

Right click the field label
Choose Show Choices
Examine the Value field to see if any have been changed from a number to -
Update if necessary

That's my initial thoughts. Let me know what you find.

View solution in original post

jbdevsn · ‎01-03-2017

Hi Chuck, I tried deleting the default value and it worked momentarily. It keeps resetting back to -- None --. Is there a way to override this?

I have also tried your other recommendations

Chuck Tomasi · ‎01-03-2017

Hi Jack,

If there is no default value, then the choice list will default to -None-. Can you help me understand what you are trying to accomplish?

toddpreece · ‎07-23-2019

Very helpful, I had an almost identical issue but found that my "unparseable error' was due to a <space> right before "Javascript..." in the default value.