Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / CRM 2016 - Required fi...
Microsoft Dynamics CRM (Archived)

CRM 2016 - Required fields at the database level

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hello,

We have a process that uses the nifty Import feature (very helpful, BTW!).  During testing, if a user uploaded a record with a blank field value that wasn't previously blank... like an OrderId... the Import feature allowed it and deleted the OrderId from the associated record.  The field is required via CRM settings, but the Import process doesn't seem to validate against that? 

I'm old school where we appropriately added value requirements at the database level, relationships, etc.  Is it possible/within best practice to still do this (like in this case) and change the allow NULL setting at the database level in the CRM database?  If so, if the Import finds an error, can it roll it back all of the changes like it would within a transaction?

Thanks for your help!

T

*This post is locked for comments

  • tw0sh3ds Profile Picture
    tw0sh3ds 5,600 on at
    RE: CRM 2016 - Required fields at the database level

    Maybe it could work as "Very business required" field :) I can't imagine that currently Business Required fields are required on DB level - all the form logic that makes some fields required based on something else would be not possible and that is quite a lot of form logic in many of the systems :)

    But anyway, the scenario that you've described is really common - I'm currently working for a company which supports many CRM deployments and in most of them some user with too high security role destroyed something because of not understanding how import feature works :)

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: CRM 2016 - Required fields at the database level

    Thanks, Joe :) I hope CRM team is reconsidering that... or it might be helpful to understand the business case as to why CRM doesn't use those features of SQL Server.  Database level reinforcement of data quality saved the day too many times in my career...lol.  Happy Holidays and have an amazing day!

  • Suggested answer
    Joe Gill Profile Picture
    Joe Gill on at
    RE: CRM 2016 - Required fields at the database level

    Hi T,

    Setting a field to required in customizations does not as you found out enforce it at database level. It is only for forms.

    Afraid you will need to add your own validation to the import routine.

    Modify the CRM SQL database adding constraints, etc is not supported

    hth

    Joe

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans