Dynamics CRM / 365, c#, MS SQL
We use Dynamics 365 online and have one question.
Assume all of the users are insurance broker. and each insurance broker has mulitple states of license (from CA to NY).
Where should the list of license store? I do not want to create custom entity because the license cost will go up.
and I also do not want to hard code state name as field like LicenseCA, LicenseTX. It is going to very hard to manage.
It will be the best to use one of entities that have 1 to M relationship to USER entity. But I do not know which ones should be used.
Please helps.
Assume all of the users are insurance broker. and each insurance broker has mulitple states of license (from CA to NY).
Where should the list of license store? I do not want to create custom entity because the license cost will go up.
and I also do not want to hard code state name as field like LicenseCA, LicenseTX. It is going to very hard to manage.
It will be the best to use one of entities that have 1 to M relationship to USER entity. But I do not know which ones should be used.
Please helps.
Chinmay Patel
How about using Connections?
ASKER
Any good reasons why?
As you said, you want to keep the license cost under check and connections provide a pretty generic and straightforward option i.e. connecting two different entities.
ASKER
I think you are right.
ASKER
my last question is entity CONNECTION - Is it commonly used for different situation? Like I have my questions about insurnace broker to many state licenses.
If I have another situation like Insurance broker to mulitple appointment (insurance company)., is it best practice to use CONNECTION entity on Dynamics? Just I have never used CONNECTION entity in the past., so I am not sure.
If I have another situation like Insurance broker to mulitple appointment (insurance company)., is it best practice to use CONNECTION entity on Dynamics? Just I have never used CONNECTION entity in the past., so I am not sure.
Connections allows you to develop relationships which are not provided out of the box.
https://docs.microsoft.com
https://docs.microsoft.com
ASKER
I read some blogs about CONNECTION entity. It is great news to me because I know I am going to use alot.
However, CONNECTION entity does not fit to my question.
Actually, I am browsing dynamics 365's entities and hope to find entities I can drop the data into. For example,
I have a record,
user(John a), license no. 1234, license state: CA, expiration date: 01/01/2019
user(John a), license no. 1234, license state: TX, expiration date: 01/01/2029
user(John b), license no. 1235, license state: CA, expiration date: 01/01/2019
user(John c), license no. 1236, license state: CA, expiration date: 01/01/2019
I just hope to find a home to stored them.
And now I know I can use CONNECTION to join them together with USER entity.
that is awesome.
However, CONNECTION entity does not fit to my question.
Actually, I am browsing dynamics 365's entities and hope to find entities I can drop the data into. For example,
I have a record,
user(John a), license no. 1234, license state: CA, expiration date: 01/01/2019
user(John a), license no. 1234, license state: TX, expiration date: 01/01/2029
user(John b), license no. 1235, license state: CA, expiration date: 01/01/2019
user(John c), license no. 1236, license state: CA, expiration date: 01/01/2019
I just hope to find a home to stored them.
And now I know I can use CONNECTION to join them together with USER entity.
that is awesome.
ASKER
and just FYI, I am thinking to use TERRITORY entity.
I am not sure about territory, I did write it in my earlier comment but I deleted it as I am not sure what implication it will have on your scenarios. If your scenario fits in to it then well and good, you can use it as well.
ASKER
can you share with your comments? I am not sure I pick up the right one
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.