You’re offline. This is a read only version of the page.
Hi,
I am trying to create a new currency field which displays at 2 decimal places:
However when I look at this new field on the form it looks like this:
and when I hover over the X it says ' A currency is required if a value exists in a money field. Select a currency and try again.'
However we have other currency fields, that are set up as above but do not look like this on the form.
Everything seems to be correct under Settings >> Administration >> System setting >> Formats
Unfortunately I was not managing this CRM when the other currency fields were created so I'm not sure of the set up, but I assumed if I created the new fields they way the existing ones were done that would be sufficient, however it doesn't seem to be the case.
Thanks in advance for any help you can provide.
Thank you,
Tanya
Thanks so much for that information.
After a bit more playing around I found out what the issue was.
I didn't realise that when I created my new field (field type currency), Dynamics also created an additional field called 'Currency'. I had added my new field to an existing record, but didn't notice the 'Currency' field which was then causing an error because it was not being populated. If I was creating a new record this 'Currency' field gets populated on creation of a record, so it wouldn't have bee a problem but because the new field was added to an existing record I needed to patch the data to stop the error from occurring.
Do you have a default currency set in your user preferences?
The below is stolen from Neil Parkhurst in community.dynamics.com/.../211409
As this is a data issue it might not be surprising that you haven't seen the problem before.
It could be down to user behaviour!
Say your custom entity is linked to account and that has a default currency set on the account. If you created the custom entity from account then the currency field would be mapped onto the custom entity and all would be good.
But if the user created to custom entity not from the account then the currency would need to come from their user options. Which if not set would mean the currency field could be blank.
It could simply be the way the users happened to create those specific records caused the problem. If you ensure all your users have a default currency set you will probably not see this issue again.
If it keeps happening you could consider having a business rule (or something) default the currency. But generally I wouldn't expect you to need that. When working with one currency, I often hide the currency as you have done and I haven't had this as a support issue often.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (