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 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 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
Does dynamics allow you to expose the contactid for each contact by publishsing the oob contactid field on the form? I am trying to accomplish this however when I go to the form and look at the available fields on the right, this oob field doesn't show up.
I also tried to trick the system by creating a new field and a workflow to copy the data from oob contact id field to this new field but surprisingly the workflow is coping the name and not the id. (Note that I have used the correct field which has contactid)
Hello there :
other one easy way is mentioned here without any script or code : www.powerobjects.com/.../how-to-derive-and-expose-a-record-guid-on-your-forms-using-oob-functionality
You can't show out of the primary key field to form, but can easily get show it in text field using on load script like below
Any idea why this is the expected behavior or why MS doesn't let you do it purposefully?
The only reason i can think of is - its not "User Friendly". No business user would want to see it on the form.
urm...One of my client has this requirement but anyway that functional way of doing it looks easy enough...THanks much :)
Okay, I implemented the way it was mentioned on that link however the new field Record URL (singlelineoftext, URL) is exceeding the maximum characters (100 by default) which eventually fails my workflow. :/
Error- A validation error occurred. The length of the 'new_recordurl' attribute of the 'contact' entity exceeded the maximum allowed length of '100'.
Any suggestions, please?
You can very well increase the length of the field from field definition.
Sorry I should have mentioned this on my last comment but dynamics doesn't let me do that. It throws a generic SQL error. I read below blogsbut still no luck :(
Unhandled Exception: System.ServiceModel.FaultException`1
<Message>System.Data.SqlClient.SqlException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #06912640</Message>
<ExceptionSource i:nil="true" />
<InnerFault i:nil="true" />
<OriginalException i:nil="true" />
<TraceText i:nil="true" />
Did you try to apply suggestion given in the thread -- "This error usually happens when the field you are trying to edit is added as a "Find Column" in the Quick Find View of the entity ".
alternatively - is there an option of deleting this field and re-creating it? if its new.
Yeah these fields are not added to any views as of now. Yeah, I can try to delete them. Did you mean recreating it and before I hit save, increase the value?
Business Applications communities