-
Automatically detect and remove orientation Metadata from marketing emails
Some images contain orientation Metadata, Windows and Marketing Email preview page both display the image in the correct orientation. However, when the image is sent to the recipient via Journey, it appears incorrectly. While asking users to manually rotate each image is an option, it would significantly increase their workload, and they might forget to do it.
-
Related table fields are not supported by Dataverse search.
We have related table fields as a View column in a table's Quick Find View. However, it is not displayed in the search results. This is a great inconvenience for the business, and it is requested that the related field be supported in the search results in a future release.
-
Enhance the Analytics that are being shown in Customer Insights Journeys
We understand that the analytics reports in marketing are generated using Power BI. However, these reports are currently not editable and cannot be tailored to meet specific business needs. We propose that users should have the ability to save Journey Analytics and Channel Analytics reports as PBIX files. And allow users to customize the report themes, add new visuals and filters based on business requirements in our Power BI workspace. Thank you!
-
The Calendar entity returns values in different JSON format for different Calendars
Some Customer service calendar Calendars have only one "calendar_calendar_rules" and some record have multiple "calendar_calendar_rules". If all working hours are the same when creating the Customer service calendar, then there will only be one “calendar_calendar_rules”. Now if we modify the working hours and save it, then it will be divided into two or more. Developers are using Calendar entity in some plugin logics to identify the Working days and hours. Since responses varies now for different Calendars, we are encountering issues with the current logic. In addition, the "calendar rule" entity is a special entity that cannot manipulate records through API. Please unify the Json format of calendar entity, otherwise this will have a huge impact on Business