MENU
what are 3 risks when using too many cross-object formula fields in a revenue cloudproject?
Suggested Answer: B
Get Premium Revenue Cloud Consultant Accredited Professional (AP-223) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
For a Revenue Cloud project where a product's taxability depends on a custom field that holds industry information, the appropriate solution is to use automation to set the Tax Rule based on the value of the custom field. This approach allows for dynamic application of tax rules to products based on industry-specific requirements, ensuring that the correct tax treatment is applied during the quoting and invoicing processes. Automation could involve using Process Builder, Flow, or Apex to update the tax rule assignments on products or quote lines based on the specified industry criteria. This ensures that products are taxed correctly according to the industry-specific regulations captured in the custom field.
32 comments · newest first
NA
Nan
11 months ago
I think E is a bit exaggerated; they’re not that computationally expensive, right?
DO
Doyle
11 months ago
I've seen formula fields hit limits before, so C is spot on.
RO
Royal
12 months ago
Wait, are formula fields really editable after calculation? That seems risky!
CA
Catherin
12 months ago
Totally agree, especially with option A!
AZ
Azalee
1 year ago
Formula fields can definitely mess with data integrity.
JE
Jeniffer
1 year ago
I recall that formula fields can be edited after calculations, which seems risky for data integrity.
GE
Gearldine
1 year ago
I’m a bit confused about the computational expense of formula fields. Does that really impact performance significantly?
AD
Adelle
1 year ago
I think one risk is that they can exceed limits if not designed properly. I practiced a question like that before.
NA
Nan
1 year ago
I remember something about formula fields being vulnerable to data changes, but I'm not sure if that's the main risk.
AN
Annamae
1 year ago
The computational expense of formula fields is an important consideration that I hadn't thought about. I'll be sure to include that in my response.
OT
Otis
1 year ago
The part about formula fields being editable after calculation is interesting - I'll make sure to remember that detail.
BE
Bettina
1 year ago
Okay, the options cover a good range of potential issues with cross-object formula fields. I'll make sure to hit the main points in my answer.
AL
Alyce
1 year ago
Hmm, I'm a bit unsure about the difference between "vulnerable to data changes" and "exceed limits" - I'll need to think through those carefully.
AL
Alpha
1 year ago
This question seems straightforward, I'll focus on the key risks mentioned in the options.
TR
Trevor
1 year ago
This question seems straightforward, but I want to make sure I understand the nuances. I'll need to carefully read through the options to determine the true statement.
EL
Elenora
2 years ago
D seems like a pretty serious issue. If the data isn't available during CPQ calculations, that could really throw a wrench in the works.
JA
Jacinta
2 years ago
Haha, Option B is hilarious. Can you imagine a Sales user just casually overwriting a formula field? Talk about a recipe for disaster!
DE
Dean
1 year ago
User 3: Option B is a good reminder to always double check before making changes.
SO
Solange
1 year ago
User 2: Definitely, it's important to be careful with formula fields.
LE
Lelia
1 year ago
User 1: I know right, that would be a disaster!
LU
Luis
2 years ago
I agree with A. Cross-object formulas are a risky business when it comes to data changes. You really have to think it through.
BE
Belen
2 years ago
Option C is spot on! Too many formula fields can definitely exceed limits if you're not careful. Better design and testing is a must.
DE
Devora
1 year ago
We need to be cautious with how many cross-object formula fields we use.
JE
Jean
1 year ago
Yes, computational expense is another risk to consider.
JO
Johnna
1 year ago
It's important to carefully design and test formula fields.
TY
Tyisha
1 year ago
I agree, exceeding limits can cause major issues.
MA
Marshall
2 years ago
Also, formula fields being editable after calculation can cause issues.
CH
Chauncey
2 years ago
Yes, I agree. It can make the project vulnerable to data changes.
AU
Audrie
2 years ago
I think using too many cross-object formula fields can be risky.
FE
Felicia
2 years ago
Yes, and the formulas can be overwritten by Sales users or automation.
JA
Jaime
2 years ago
I agree. It can lead to data changes and limits being exceeded.
DE
Denny
2 years ago
I think using too many cross-object formula fields can be risky.