Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

d365 v9.1 onprem model driven app lookup field bug?

(0) ShareShare
ReportReport
Posted on by 702

D365 v9.1 onprem

Customized Model Driven App

Custom Entity main form

Account lookup field is a required field, if user click on save or save & close button it displays the "Required fields must be filled in." error message.

so far so good, but from there onwards, if user search for a account that is not found. The lookup field kept giving the " "Required fields must be filled in."  message 

instead of the normally expected "No records found. Create a new record."

This feels like a D365 bug. I wonder if any of you have experience it? if not and if you are on v9.1 onprem, could you let me know what service pack you are on please?

our current Version 2104 (9.1.1.914) (DB 9.1.1.914) on-premises

Client version: 1.4.2546-v91onpremise

Cheers

Xun

  • Leco Lv Profile Picture
    Leco Lv on at
    RE: d365 v9.1 onprem model driven app lookup field bug?

    Hi partner,

    I tested it on the dynamics  online version.

  • shennu Profile Picture
    shennu 702 on at
    RE: d365 v9.1 onprem model driven app lookup field bug?

    Thanks for your response and the confirmation of the behaviors.

    May I ask with version are you on? online or on-prem?

    Cheers

    Xun

    Regarding "it's not a bug because it doesn't affect any functionality" I see what you mean but It is clearly giving a miss misleading notification to an end user...

  • Suggested answer
    Leco Lv Profile Picture
    Leco Lv on at
    RE: d365 v9.1 onprem model driven app lookup field bug?

    Hi partner,

    I tried to reproduce your problem according to your description. At the beginning, my field was not set as required. It met your expectation and displayed "No records found. Create a new record". but after I set it as a required field, it kept giving the " "Required fields must be filled in."  message.

    I don't think it's a bug because it doesn't affect any functionality. You can put forward your suggestions on Microsoft ideas.  The only way currently is to remove the required attribute.

    At the beginning:

    pastedimage1668572789520v1.png

    I set it as a required field:

    pastedimage1668572807416v2.png

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 Verified Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 230,492 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans