Comments
Transaction currency is required at this point,Also reporting currency should be included. If Dynamics support reporting currency, there should be a rate for reporting currency, and the mount data from reporting currency should be tracked as well. The short term account balance, the recognitin amount balance should be calculated based on the reporting currency.
Duplication rules in general are a total mess in Dynamics. It's incredible limited in options, there is no "fuzzy" match logic, it's not possible to exactly define who can merge which records, Users can simply ignore it, it's not possible to combine data, but only to replace and then they only execute on save and not on opening records. This needs to be addressed!
This is something that should be added with high priority. It took us 4 days after or first go-Live to replace the OOB field with a custom one to ensure all Records are traceable. It's actually one of the most linked tables in the whole CRM for us, so it's really hard for me to understand that this is not standard.
Another vote to provide Lead audience options. Based on our Contact protocol that requires additional data fields, we are unable to use Event Planning functionality without a Lead audience option. Not having that option available to use in Customer Insights-Journeys limits the Marketing team to Event Tracking manually via spreadsheets and losing time and visibility into sales opportunities.