Warn of bad field names in Data Map

OL Connect Professional Feedback & Feature Requests
1

The Data Mapping module allows field names with “#” and “/” characters, which of course fail at the “Execute Data Mapping” workflow step.

My request is that these characters not be allowed, or if there is some Use Case that argues for them, to alert the user via a warning dialog.

1 Like
2

Hello TDGreer,

The limitations on the field name do not apply when printing directly from the Designer, which is why I think there isn’t forced validation currently.

However, I agree that there should at least be a warning in the datamapper if there won’t be forced validation on the field name.

I’ve made an internal improvement request for this.

Thanks,