Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam CRT-101 Topic 6 Question 68 Discussion

Actual exam question for Salesforce's CRT-101 exam
Question #: 68
Topic #: 6
[All CRT-101 Questions]

Contribute your Thoughts:

Phyliss
2 months ago
That's a good point, Visualforce could be the reason behind the field type change restriction.
upvoted 0 times
...
Kati
2 months ago
I think it might be Visualforce, as it can also reference fields in the Salesforce platform.
upvoted 0 times
...
Theron
2 months ago
Ah, the old 'Visualforce Voodoo' strikes again! Those pages can really tie your hands when it comes to field type changes.
upvoted 0 times
Flo
2 months ago
B) Record types
upvoted 0 times
...
Bette
2 months ago
A) Formula fields
upvoted 0 times
...
...
Cherri
3 months ago
Haha, I bet it's the 'Invisible JavaScripts' that are prCherrinting the field type change. You know, the ones that hide in the shadows and wreak havoc.
upvoted 0 times
...
Mammie
3 months ago
I'm going with JavaScript. You know those sneaky little scripts can really mess with your fields.
upvoted 0 times
Kasandra
2 months ago
Maybe we should check if there are any formula fields affecting it as well.
upvoted 0 times
...
Maynard
2 months ago
I agree, Visualforce can be tricky to work around.
upvoted 0 times
...
Gwen
2 months ago
I think it might be Visualforce that's causing the issue.
upvoted 0 times
...
...
Phyliss
3 months ago
But the custom picklist field is used in multiple record types, so it makes sense that it's them.
upvoted 0 times
...
Sherman
3 months ago
I disagree, I believe it's record types that are causing the issue.
upvoted 0 times
...
Phyliss
3 months ago
I think it could be formula fields that are preventing the change.
upvoted 0 times
...
Adelina
3 months ago
My money's on the formula fields. They're always the culprit when it comes to field type changes.
upvoted 0 times
...
Derrick
3 months ago
Nah, I bet it's the Visualforce pages. Those things can really lock down your fields.
upvoted 0 times
Elke
2 months ago
User 3: Maybe it's a combination of Visualforce and Javascript.
upvoted 0 times
...
Azzie
2 months ago
User 2: I think it might be the Record types causing the issue.
upvoted 0 times
...
Belen
3 months ago
User 1: Yeah, Visualforce can be tricky like that.
upvoted 0 times
...
...
Val
3 months ago
I believe it's more likely that Visualforce is the functionality causing the issue.
upvoted 0 times
...
Lasandra
4 months ago
Hmm, I'd say it's probably the record types. Those can be tricky when it comes to changing field types.
upvoted 0 times
Michael
3 months ago
No, I'm pretty sure it's the record types that are causing the problem.
upvoted 0 times
...
Maynard
3 months ago
I think it's actually Visualforce that's causing the issue.
upvoted 0 times
...
...
Cecil
4 months ago
But could it also be because of record types?
upvoted 0 times
...
Hildegarde
4 months ago
I agree, formula fields often have dependencies that prevent changes.
upvoted 0 times
...
Ryan
4 months ago
I think the field type can't be changed because it is referenced by formula fields.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77