I have a large, complicated assembly for custom pricing. I also am building a Dual Write environment based on the current solution.
I don't want to fork the code for the pricing plugin to accommodate a new DW field on the Oppty/Quote/Order header. This field is additional charges which needs to be included in the sum for the order Total.
Somehow I must trap the fact that this field is not in the metadata if I am to use the same assembly to work in both environments.
How would YOU do this?
TIA
Sorry, after starting in what I thought was a replacement/renamed forum (Sales) I found my way back here and worried that I had addressed the wrong audience.
I have a large, complicated assembly for custom pricing. I also am building a Dual Write environment based on the current solution.
I don't want to fork the code for the pricing plugin to accommodate a new DW field on the Oppty/Quote/Order header. This field is additional charges which needs to be included in the sum for the order Total.
Somehow I must trap the fact that this field is not in the metadata if I am to use the same assembly to work in both environments.
How would YOU do this?
TIA
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (