Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have a customer that has the credit limit field in the customer form (credit and collections fast tab of the customer form) is grayed out and unavailable. This is the case for all users even those that have system administrator security role. From what the partner has suggested, they state that they are using a “prospect to cash”. (which I assume is referring to a CRM > AX integration), and that this issue happened when they run accounts integrations all account in AX have the credit limit field become uneditable.
there is no way around this, no flag we can change in AX to make the field editable again? It is strange that the accounts that are created in AX and do not exist in CRM we still cannot edit the field
Can't you do it in CRM or can't you do it in AX? IF it's AX, you might want to ask the same question in the AX forum..
I am not sure that this is a Dynamics CRM issue, but an AX issue.
As Alex answered, please post this in one of the AX forums:
Hope this helps.
thanks for the reply
Yeiner, were you able to have a work around this problem?
Business Applications communities