Ken,
For the detail info you can see those links provided before, then answering your question:
"what I have not really clear is if this inputs are related each other and how they work?
Do I need to add a reference or do something more?"
As long as the entities are related then it is fine.
For example there are 2 entities:
Account and Project
Then, you have two identical fields:
Industry in both entities with same global optionset.
And also
Which you want to mapping those fields. If you create a project from relates Account Classification or Account level field and address field that you want to inherit
Then once you are in the account form then you go to Project subgrid or associated view then you create a new Project record from that Account
Sample data:
Account
Name = Bank of England
Industry = Banking
Level = Platinum Class
Address = St Louis 23, Newcastle
Then you have a new Project MS Dynamics CRM implementation in that bank you want to make sure that once you or users create the new project will be by default those fields are auto populated.
So you need to define those fields in the mapping in your 1 to many Account and Project relationship.
The things that you need to make note are:
- You only can do mapping from the related entities, this is the main concept
- Mapping is only works from Parent to Child, cannot from child to parent
- Mapping only works for the fields that are having same types and if you want to map the optionset field you must define as global option set, you cannot inherit lookup to option set and vice versa
- it will work if only you create the child record from the parent, through subgrid or associated view, it wont work if you create the project outside the parent from blank form then you later key in account field, it wont inherit the fields mapping define before.
Hope this helps!
Thanks
