Share
ReportSet up Field in different Entity with same Name and Display Name, but different "Business Require" and data type, it will cause a confliction? Thanks.
Categories:
You’re offline. This is a read only version of the page.
353
Set up Field in different Entity with same Name and Display Name, but different "Business Require" and data type, it will cause a confliction? Thanks.
Hi Goutam and Arun, thank you so much for your reply. now I understand most of issue. See you soon.
Hi ,
I believe you are aware that when creating field with same name in different entities nothing but you are creating same name column in different table in database. So there is no question of confliction in UI level.
Global variable in JS you will get only when you page/ entity form is load and till that time you make page open.Once you navigate to other pages or entity form you will not get the global variable declared in previous page.
There is no relation between field name and global variable.
I am still not clear where is your doubt?Please give some more information if above does not answers your questions.
We are doing this everyday. Don't worry. Can you explain your js global variable scenario with code sample?
But I still concern about that of the confliction, especially it will be a global var in the JScript code. Any information can convice me, please, thank you.
Hi,
You can define same field name in different entities without any issue. Even if you look Dynamics CRM OOB also having same field like publishername_name in most of the entities.
Yes, your example also works fine.
If you are going to map the 2 fields in relationship so that it can auto populate when you are creating Contact associated grid from Account, that won't work because of datatype mismatch.
Still you can pull the value from Account using OData/Web Api & populate in textbox on Contact form load.
For example, Creat a field named Age. In account entity, Age field is business require and data type is text; in contact entity, it's Optional and data type is Decimal.
You can do that without any issue. They are physically 2 different fields in 2 different entities with different data type & business requirement.
For ex, new_gender can be created in 2 different entities like picklist in one entity & 2 options in another.
I mean same name field in defferent entity with different data type and business requirement. Can I do that?
What do you mean? You want to create duplicate relationship with another entity but the lookup has to be optional?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (