MENU
Northen trail Outfitters (NTO) wants to change the current master-detail relationship between Shipments and Opportunity to a lookup relationship. The system administrator has made the necessary changes in a full sandbox and has successfully tested them against NTO's data.
Now that the changes are ready to implement in production, what should the system administrator do next?
35 comments · newest first
LA
Lamar
11 months ago
Not sure about B, unmanaged packages seem unnecessary here.
DE
Deeann
11 months ago
Wait, can you really just make changes directly in production?
LE
Lea
12 months ago
Totally agree with D, change sets are safer.
KR
Kristin
12 months ago
I think A is risky, better to use change sets.
DE
Devon
1 year ago
D is the way to go for deployment!
IO
Iola
1 year ago
I feel like creating an unmanaged package could be overkill for this situation. Change sets seem more straightforward for just a relationship change.
LE
Lenna
1 year ago
I practiced a similar question where we had to deploy changes. I think using an outbound change set is the right approach for this scenario.
CR
Craig
1 year ago
I'm not entirely sure, but I think making changes directly in production could lead to issues. We should avoid that if possible.
DE
Delisa
1 year ago
I remember we discussed the importance of using change sets for deploying changes to production. It seems like the safest option here.
ME
Meghann
1 year ago
I feel pretty confident about this one. Based on the information provided, the best course of action would be to add the components to an outbound change set and deploy it to the production org. This is a standard and well-documented process for making changes to a production environment.
MI
Mitzie
1 year ago
Okay, let me think this through. Since the system admin has already tested the changes in a full sandbox, that's a good sign. I think the safest bet would be to use an unmanaged package to distribute the changes to production. That way, we can ensure everything is working as expected before making the changes live.
TH
Thad
1 year ago
Hmm, I'm a little unsure about this one. I know we need to be really careful when making changes to the production environment, but I'm not sure if a change set is the best option here. Maybe an unmanaged package would be a safer approach?
FA
Fabiola
1 year ago
This seems like a pretty straightforward question. I think the key is to remember that we should never make changes directly in the production org, as that could cause major issues. The best approach here would be to use a change set to deploy the changes to production.
GL
Glenn
2 years ago
I'm all for the 'D' solution. It's like a surprise party, but for your production org. Gotta keep that place on its toes!
TY
Tyisha
2 years ago
Wait, we're talking about production changes? I thought this was just a sandbox exercise. Let's be careful and follow the proper deployment process, folks!
TA
Tammy
2 years ago
B) Create an Unmanaged Package to distribute to production.
WI
Willetta
2 years ago
D) Add the components to an outbound change set and deploy it to production.
RE
Reynalda
2 years ago
A) Make the changes directly in the production org.
PE
Percy
2 years ago
Option A is the fastest, but also the riskiest. I wouldn't recommend making changes directly in production unless it's a true emergency.
VA
Vanda
2 years ago
I'd go with option C. Using Data Loader is a straightforward way to export the changes and import them into the production org.
ZA
Zack
2 years ago
D) Add the components to an outbound change set and deploy it to production.
VO
Vonda
2 years ago
C) Use Data Loader to export the changes to the production org.
TA
Tamekia
2 years ago
B) Create an Unmanaged Package to distribute to production.
MI
Mireya
2 years ago
A) Make the changes directly in the production org.
PA
Paris
2 years ago
Option B seems like a good choice. An unmanaged package would allow you to distribute the changes to multiple production orgs if needed.
NA
Natalie
2 years ago
I think using a change set might be a safer option to ensure everything gets deployed correctly.
ST
Staci
2 years ago
D) Add the components to an outbound change set and deploy it to production.
JI
Jin
2 years ago
That sounds like a good idea. It would make it easier to deploy the changes.
ST
Stephania
2 years ago
B) Create an Unmanaged Package to distribute to production.
ZO
Zona
2 years ago
I think option D is the way to go. Using a change set ensures that the changes are properly reviewed and approved before being deployed to production.
LA
Lashawn
2 years ago
I always prefer using change sets for deploying changes, it gives me peace of mind.
FE
Felicia
2 years ago
It's important to have a proper review process in place before making changes in production.
RO
Rodolfo
2 years ago
I agree, using a change set is a safe way to deploy changes to production.
MO
Mozell
2 years ago
I agree with Felix, using an outbound change set is the safest way to implement the changes in production.
FE
Felix
2 years ago
I think we should add the components to an outbound change set and deploy it to production.