A currency is required if a value exists in a money field. Select a currency and try again

(0) Share

Report

Posted on by Cyclefitness

We are experiencing this issue on a custom entity in our QA 2016 Online instance. I've researched that many others encounter this issue, but the solutions don't align with our scenario. You see, in our situation, this entity and it's Main form work perfectly in one instance. But when we migrate it to another instance -- QA --, it doesn't work, so it can't have anything to do with the form missing a currency field.

I have confirmed the instance has US Dollar currency as its only Active one. How to resolve this error?

381375.1.png

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Suggested answer

Archer Mehrab 186 on at

Like (0)

Report

RE: A currency is required if a value exists in a money field. Select a currency and try again

Hi Every one,

I just had the similar issue while creating the record through SSIS package on the custom Entity, and how I did overcome on the issue, and I thought it is better to be shared with other peers which could save sometimes.

Generally any Money Related field having the currency field attached to it, which that currency filed needs to have value while creating the record , and it is very obvious for the CRM to assign the value of the Currency based on the User Profile , but when you migrate the data from another instance, you need to migrate the currency as well with it and the Value of the Price field would not be enough for the migration ( SSIS is one of the examples of Migration of the Data which could cause the issue )

Solution: Passing the GUID number of Currency to the Currency field and Run your Migration package again

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: A currency is required if a value exists in a money field. Select a currency and try again

I wanted to make sure I added to this thread that Neil's answer solved my problem as well. Other records for my custom entity worked fine, but the one I was focused on for the purposes of a demo in a trial environment didn't have a value. I've been the primary user of this relatively new Dynamics 365 trial environment and the value just ended up blank somehow. No idea how it happened as I initially created the record (shrug). Thanks!

Was this reply helpful? Yes No
Suggested answer

Neil Parkhurst 10,727 User Group Leader on at

Like (0)

Report

RE: A currency is required if a value exists in a money field. Select a currency and try again

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.

Was this reply helpful? Yes No
Cyclefitness on at

Like (0)

Report

RE: A currency is required if a value exists in a money field. Select a currency and try again

Neil:

I have had my solution working for almost 8 months now and this is the first time I've seen this. It does not appear like this in one online instance, but appeared when we migrated to another. Could this value be being dropped during migration>

In any event, I created a dummy form with just the currency field and noticed that some of the records had a value and some others did not. Why would that ever happen and how does the value get there to begin with? Once I populated that value on every record, the error disappeared. And when I create a new record, US Dollar is defaulted. Not sure how any of those ever lost that value.

Thank you for your help!

Was this reply helpful? Yes No
Verified answer

Neil Parkhurst 10,727 User Group Leader on at

Like (0)

Report

RE: A currency is required if a value exists in a money field. Select a currency and try again

Your currency field is most likely blank. Try adding this to the form to see what it contains.

You may need to ensure the users default currency is set in options.

Say this is a custom entity coming from account you may also need to check the default currency on the account. Or other parent record.

Was this reply helpful? Yes No
Suggested answer

Luke Sartain 1,266 on at

Like (0)

Report

RE: A currency is required if a value exists in a money field. Select a currency and try again

A bit of long shot but do you have a default currency set in the problematic instance for the user? Just wondering if in your other environment you have one set which is being used when the record is created and the reason you're not seeing the error there, much like when you create a new Account it defaults to this currency.

Was this reply helpful? Yes No
Cyclefitness on at

Like (0)

Report

RE: A currency is required if a value exists in a money field. Select a currency and try again

This entity and its forms work fine in another environment. It's only when migrating to a different online instance that this appeared.

Was this reply helpful? Yes No
Suggested answer

Larry Merkelis 225 on at

Like (0)

Report

RE: A currency is required if a value exists in a money field. Select a currency and try again

Hi Debra,

the way this works is that you have to have the Currency field on the form if you have any fields of currency type.

By default it would be set to default currency for all new records, but existing records will have a value of NULL so you will need to update them.

Hope this resolves your issue

Was this reply helpful? Yes No