Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
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
i have a Extend table in the HCMPosition fields <PositionId> is there by default mandatory "Yes" i need it set to "No" for that in the TableExtension We can edit the XML file
What is the tag to change the mandatory property to No?
Riyas Ahamed F
Some properties cannot be modified by extending the table, but you can change it by code.
Please refer this thread:
Thanks for your replay Blue wang, it is possible edit by XML? if yes let me know.
Riyas ahamed F
Modifying XML can meet the needs, but that's not a reliable way
You can not change this to No using extensions. Certain properties are not extensible. Modifying xml is not the correct way , Its might work in your dev machine but its not going to work in environments where you deploy binaries like prod or UAT.
Thanks for your valuable Answer Sukrut,
Currently, i am using Demo VM, so please let me know What is the tag to change the mandatory property to No?
it is my test purpose only.
Well , even if it is for test purpose i wont recommend you to change XML file. You can change it , if you just want to experiment see what it does or what impact it makes and revert back .
Another thing is positionId is primary key in HCMPosition table and it is required to be filled in, so it does not make sense to make it non mandatory.
You can't change mandatory fields to not mandatory via extension. And as pointed out, in this case it's a field in the primary key so you could not enter more than one record in the table with empty position id.
Another important point is that the standard functionalities trust that this field always has value. You would not want to break the system, right?
Just use the Visual Studio to do the dev work. And don't try to "hack" your way around the system rules. I'm sure your customer wants a stabile system, not a system with hacks and broken functionality.
Business Applications communities