Unparseable number error when creating a new change

[frappe]

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

[ramireddy]

It seems to be some one might changed "value" of choices of 'impact' column in change_request table. Values supposed to be "1","2","3". Check they sare same or changed?

[Chuck Tomasi · Accepted solution]

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.

[frappe]

Ok, it turns out that the dictionary default value was literally "- None -" ... I assumed if the field was blank that the default value would be blank.   Once I deleted "- None -" the issue went away thank you very much !

[Chuck Tomasi]

Thanks for getting back, posting your findings, and participating in the community.