Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Answered

Edit Standard DCRM Fields or create a new one?

(0) ShareShare
ReportReport
Posted on by 50

Is it better to create a new field or edit a standard field in DCRM 365?  (Ex. Relationship Type and Industry fields)  Both of these are what we are looking for but we would need to remove and add info to each.  What is the best practice?  Create brand new fields and remove these from the Form or manipulate these current system fields?

  • Verified answer
    Charles Abi Khirs Profile Picture
    Charles Abi Khirs 3,569 on at
    RE: Edit Standard DCRM Fields or create a new one?

    Create a new field for industry and Add your options to it

  • KP2 Profile Picture
    KP2 50 on at
    RE: Edit Standard DCRM Fields or create a new one?

    I guess i should have been more specific...it will still be an Industry field.  We would only remove and add different options to that field.

    Thanks,

    Kyle

  • Verified answer
    Charles Abi Khirs Profile Picture
    Charles Abi Khirs 3,569 on at
    RE: Edit Standard DCRM Fields or create a new one?

    Hello,

    It depends on the field that you need. As for the recommendation, it is always better to look first if there is similar existing field that can be used rather than creating new one.

    You should consider if the existing field is used in the OOB reports, charts, views... if this is the case, it is better to create new field.

    In addition, take into consideration if there is a lot of difference between the existing values and the ones you need, if this is the case, go with a new field.

  • Verified answer
    rthompson Profile Picture
    rthompson 1,530 on at
    RE: Edit Standard DCRM Fields or create a new one?

    Hi,

    I would say the best practice is not to change a OOB field to do something that it was not design for.

    The reason why is because if you start storing data in the OOB field and 2 years down the road you need to start using that OOB field.  Now you will need to create a new field and copy the data from the OOB field to the new field.

    Use the OOB field base on what it is used for and create a new field when need.

    It will save you a lot of time down the road.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,356 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans