Comments
This would be a game changer and I'm shocked it's not yet considered. The amount of data being loaded throughout the day from the APIs is unnecessary. This is something that is highly needed. Refresh times are out of control and we're only 5 months into BC. I'm scared what 12 months will look like.
When managing a Journey, we are unable to edit Segments that are attached. Currently, the only option is to end the Journey and Launch a new version. This is impractical as Journey participants may reenter new journey due to the fact it is a new Segment and Journey. I should not have to build additional suppression lists to make a small edit like changing a referenced field in a segment.
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.