A custom pricing engine for a Salesforce customer has to be decided by factors with the following hierarchy:
State in which the customer is located
City in which the customer is located if available
Zip code In which the customer is located if available
Changes to this information should have minimum code changes
What should a data architect recommend to maintain this information for the custom pricing engine that is to be built in Salesforce?
Currently there are no comments in this discussion, be the first to comment!