MENU
A company sells and services bicycles. The company uses Dynamics 365 Sales and Dynamics 365 Customer Service. You create a custom table named Bicycle
A user tries to create a personal view with information from the Bicycle table. The user wants to add customer information from the Account table, but the columns are unavailable
You need to make the Account columns available to the Bicycles table.
What should you configure?
Suggested Answer: A
Get Premium MB-230 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
26 comments · newest first
VI
Viola
11 months ago
Can you really just create a relationship like that? Sounds too simple.
LE
Leota
11 months ago
I’m surprised this isn’t more straightforward.
NE
Nelida
11 months ago
Wait, why not just add the columns to both tables? Seems easier.
CA
Cathern
12 months ago
Totally agree, option A is the way to go.
HA
Harley
12 months ago
You need to create a relationship between the tables!
VI
Virgina
1 year ago
Creating separate views doesn't seem efficient. I think we should focus on linking the tables instead.
PH
Phil
1 year ago
I feel like we discussed the importance of user roles, but adding the system administrator role seems too broad for this issue.
BA
Barbra
1 year ago
I'm not entirely sure, but I remember something about needing to add columns to both tables. Maybe that's an option?
EA
Earlean
1 year ago
I think we need to create a relationship between the Account table and the Bicycles table. That sounds familiar from our practice sessions.
GR
Gregoria
1 year ago
Adding the system administrator role to the user ID? I don't think that's the right solution here. That doesn't seem relevant to the problem of connecting the data between the tables.
CL
Claudia
1 year ago
Okay, I've got an idea. Creating a relationship between the two tables should allow the user to access the customer information they need in the Bicycles view. That seems like the most logical solution to me.
JA
Jamal
1 year ago
Hmm, I'm a bit confused. I'm not sure if adding the same columns to both tables is the right approach, or if creating separate views is the way to go. I'll need to think this through carefully.
LA
Lashawnda
1 year ago
This seems like a straightforward question about connecting data between tables. I think the key is to create a relationship between the Bicycles and Account tables.
FR
Franklyn
1 year ago
I'm leaning towards option A, creating a relationship between the tables. That's the most direct way to make the Account data available in the Bicycles view. The other options don't seem quite right for this scenario.
LI
Lindsey
1 year ago
Hmm, I'm not entirely sure about this one. I'll need to think it through carefully to make sure I understand the RemoteApp feature correctly.
TE
Terina
1 year ago
I've seen this type of SAML 2.0 setup before. The solution seems straightforward - separate the SSO and provisioning functionalities into two different app instances.
AR
Art
2 years ago
I think adding the system administrator security role to the user ID of the salesperson might also help.
MA
Marilynn
2 years ago
I agree with Gene, creating a relationship would make the most sense.
YO
Yolande
3 years ago
But wouldn't it be easier to just add the same columns to both tables?
GE
Gene
3 years ago
I think we should create a relationship between the Account and Bicycles table.
BE
Bettina
3 years ago
Exactly! Better to do it the right way and create the relationship. That's the cleanest solution in the long run.
VE
Veronika
3 years ago
Agreed. I'm going with A. The question specifically asks how to make the Account columns available, and creating the relationship is the way to do that.
MA
Margot
3 years ago
Agreed. I'm going with A. The question specifically asks how to make the Account columns available, and creating the relationship is the way to do that.
OL
Olen
3 years ago
A) Create a relationship between the Account table and the Bicycles table.
MA
Mattie
3 years ago
Hmm, that's a fair point. But I think adding the columns to both tables would be a bit of a hack. It's not really the intended way to handle this type of situation.
CH
Chanel
3 years ago
Haha, yeah, I can just imagine the chaos if we start duplicating columns all over the place. That would be a maintenance nightmare!