Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I am getting an error that my value is not set between the min and max currency level when I try to make a change in the editable grid for a custom field in a custom entity. The error also pops up for the currency field if I try to edit another field, like notes, and the currency field has a value already (only when in editable grid). If the currency field is blank, and I edit the notes or any other field beside the currency, there is no error and it saves properly.
When I go into the record, I can make the change to currency and save the record without any issues. Has anyone experienced this before with editable grid? It has been working fine and recently stopped working.
No system changes have been made. Currency is set to US Dollar for all Users system wide. I tried creating a new currency field and it caused the same error.
Here is the error coming up:
Here is the field set up:
Hi MS Helper,
Can you make sure you are not displaying the field name with "_base" as the suffix? It appears this is what you are doing based on the error message. You should be using the field without the "_base" at the end.
Hope this helps.
I am using the actual cost field w/o base.
I have added them both into the view so you can see the error.
Thanks. Are you version 9.0? I will try in my instance and see if I get same error...
No, we are still on 8.2 but we have our scheduled upgrade to V9 this week.
I just tested in version 9 and I could not break it. :)
I tried entering the $ even to see if I could break and I could not. It allowed me to enter negative / positive values and everything worked fine.
Now, the interesting thing with V9 is that I entered a value "much higher" then the max value and it converted the value to the max, it did not give me a message or anything, just set the value to the maximum, see below:
This is different behavior then what happens on the standard form where I get a message / error that I am over the max:
So I would bet this behavior will change for you in a couple weeks but not sure if it will change the way you want :)
Hope this helps!
Also, just saw another related post on same issue. I updated this one with the notes relating to this as well.
Microsoft contacted me informing me that this was a known issue that have been resolved by the development team.
However, it will first be available on the next service update, later in July.
While this affect the editable grid, it does not affect the forms and can still be edited as normal there.
Thanks Drew. We rolled out V9 last night and we are up and running today. The issue no longer persists in V9.
Business Applications communities