Formula Field Parity across features

Thanks for the post @alizee. I’ve always wanted to write something similar but never found time for it. Though I understand why the options in report builder are limited/different, I’d want to have same formula builder experience in Data Management, Data Designer & Rules Engine 

ALSO

WHY can we not create formulas that result in a currency data type? I want to calculate MRR… and I need it be a currency data type for obvious reasons… 😭

I link your post here @alizee and it’s in the comments too, but I also created an extension of this thread here that maybe should have just been a comment on this post but oh well:

• Please improve Object Level Formula Fields New Idea
• 17 Votes

Hi @alizee and everyone,

I’ll address each aspect of it differently

• In Reporting and GDM, the formula is stored and the data is calculated on the fly - so some formulae that are compute intensive - we will not want to give them here since the reports would time out. Where as in Data Designer / Rules / JO, its pre-computed, i.e. data is calculated and stored in store. Hence we can give more here on principal. 
• UX - We have improved our Horizon formula builder - @Aayaan from our design team lead that and we are using the same formula builder across Reporting and DD. So its literally the same component and same experience.
• Enhancing Formula builder for currency and percentage data types - This is an enhancement we want to take in the medium term. 

Hi all - just wanted to add something here:

• Calculated fields in Data Designer can leverage data from lookups. 
• Calculated fields in Data Management cannot. We are migrating to relationships and this would really, really be needed where we fetch an established value for the company but need to calculate something at relationship level (I’m going for the workaround route but still wished it would be a thing). 

Thanks!

A