Look Up Fields
- Ok this is my last question. I am running CRM v.3.0 When I create a field, can I set it up as a Look up field? (This would make my life much easier with our sales guys :-))
Answers
- Hi,
Looks like you still need a 1-to-N relationship. By customer, I believe you are referring to an account in CRM terminology.
The primary entity (1 of 1-to-N) of such relationship is the entity that you want to add such lookup to its form, the related entity should be account.
Create the relationship first, and then you will have a new lookup attribute which you can add to your form.
Cheers,
Daniel Cai | http://danielcai.blogspot.com- Marked As Answer byDonna EdwardsMVP, ModeratorSunday, November 15, 2009 5:06 PM
All Replies
You need to create relationship first. Then add the lookup attribute to your form.
Hope this helps.
Daniel Cai | http://danielcai.blogspot.comYou need to create relationship first. Then add the lookup attribute to your form.
Hope this helps.
Daniel Cai | http://danielcai.blogspot.com
So if I create the field, what relationship would I create? Sorry for the elementary question, I am just trying to set this up correctly. Thank you for your help.
Sincerely,
Shannon- It should be one-to-many relationship. After you have created the relationship, a lookup attribute will be created, which you can add to your form.
Cheers,
Daniel Cai | http://danielcai.blogspot.com - I keep getting an error stating that I have not created a custom entity.
On the opportunity form, I need to have Company and Contact fields, so I wanted to just create a new contact field as a lookup field. I am guessing that I am just missing something. Thank you again for your help. - If you're after a field where the user can select from a set of values, use the picklist format. no relationships required. If you want to use a lookup to reference another record in CRM, this is when you'll need to create the relationship between entities.
Leon Tribe
Want to hear me talk about all things CRM? Check out my blog
http://leontribe.blogspot.com/
or hear me tweet @leontribe
Want to hear me talk about all things CRM? Check out my blog http://leontribe.blogspot.com/ or hear me tweet @leontribe- Proposed As Answer byLeon TribeMVPFriday, November 06, 2009 7:22 PM
- Hi Shannon,
Leon is right, picklist seems to be better solution for your case. In CRM world, we use lookup to refer to a 1-to-N relationship.
Cheers,
Daniel Cai | http://danielcai.blogspot.com - So I should use a picklist to choose a customer that is already in CRM? I will look at doing that now, I thought it would have to be a look up field or I would have to specify everyone (which would be an impossible task). Thank you both
Sincerely,
Shannon - Hi,
Looks like you still need a 1-to-N relationship. By customer, I believe you are referring to an account in CRM terminology.
The primary entity (1 of 1-to-N) of such relationship is the entity that you want to add such lookup to its form, the related entity should be account.
Create the relationship first, and then you will have a new lookup attribute which you can add to your form.
Cheers,
Daniel Cai | http://danielcai.blogspot.com- Marked As Answer byDonna EdwardsMVP, ModeratorSunday, November 15, 2009 5:06 PM
