No Name in the lookup field

(0) Share

Report

Posted on by Bhavya E

Hello Everyone,

I am working on D365 online version , I created contact lookup in the application entity (Custom Entity) .

I am getting no name for the contact in application entity

No js is running on form Onsave

Please help me to resolve this issue

Thanks In advance

I have the same question (0)

All responses (3)

Answers (0)

LeoAlt 16,331 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi partner,

Could you share some more informations to descrip "no name for contact" ?

1.If you mean there is no contact records in your lookup filed, you need to check the contact lookup view filter condition or click on "change view" to choose other views and test if the contact look up field in other entities are correct.

2.If you mean you could not see the contact's name in lookup field, you should check the contact looup view The three left-most fields because the records in lookup view on show the three feilds.

If my understanding is not correct, please share more details like screeshots so that we could help you in a easier way.

Hope it helps.

Best Regards,

Leo

Was this reply helpful? Yes No
Bhavya E 17 on at

Like (0)

Report
Copy link

Link copied!

Hi Leo Zhang ,

Thanks for the reply ,

There are lookup records in the view and Able to select the record from the lookup list. but when I save the record , it removes the selected record and saves the record with No Name

----> This is Before saving Able to select the record from Dropdown

------> This is after saving the record

Was this reply helpful? Yes No
LeoAlt 16,331 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi parnter,

Thanks for your details.

Accroding to your decsriptions, please refer to the following reasons.

1.If there is any business rules which could change the lookup value when reload the form.

2.Please enable the field audit of this field and when the value change to "no name", check the audit history and see if the modifier is yourself. If not, that means someone else's workflow changes the value of your field.

3.Check the system job after you saving the record and see is there a workflow running related to your entity.

Hope it helps.

Best Regards,

Leo

Was this reply helpful? Yes No