Ideas - ClickDimensions Marketing Automation for D365

Submit your Product Ideas to the ClickDimensions Product Management Team below.

These will be reviewed for consideration in a future product release. It is not intended to provide Product Support. If you are having a product issue, please follow regular support procedures.


Thank you for taking the time to submit your thoughts!

Ensuring that our products address the needs of our customers is important to ClickDimensions. By providing your input, you're helping us ensure that our products are built by Marketers, for Marketers.


Information about the Product Ideas portal can be found in this support article.

To submit ideas related to ClickDimensions Intelligent Dashboards please go to this link.

Generate import template based on views including custom fields (other than text fields)

Hi,


For some mysterious reason, we've been facing problems with our Dynamics import process for months now, and their support is still looking for it.

We really were hoping that we could avoid that problem by importing / updating our contacts through the ClickDimensions import.

Sadly, we're blocked by the fact that the import template doesn't reflect the fields we use (aka the ones we chose to display in our contact views). We mainly need to add custom 2-options fields, which we can't as it is only possible to add custom text fields today.


One way to solve this would be to enable the addition of any other type of custom field.

As you could hesitate to implement this because more custom field types could create more complexity in using the import tool (leading to support sollicitation and potential customer insatisfaction), maybe one way of facilitating it would be to generate automatically custom import templates.

Those templates would be based on the different views / fields (whether they would be custom fields or not) used by the customer.

That way, the customer would only have to download the import template and complete it with the right values (ideally displayed value names, not technical ones).


I would also suggest to make sure that the generated template field names are coherent with the display names, or at least the schema names the customer has for it in its CRM.

For example, as a French customer, most of my display and schema names are in french. Yet, the current template field names are in english, without any obvious correspondance in my CRM. If I could match most of them easily by understanding the translation , it was way trickier for other fields my predecessors had modified. I had no other way but to check / test each one of them to understand the mapping.


I also take this opportunity to thank you for your work, as well as the work of your Support Team who tried its best to help us.


  • Sixtine Chapron
  • Jul 30 2021
  • Attach files