Inconsistent auto mapping of excel fields to frontend fields w/wo underscore for some custom fields. It seems like not all custom fields are available as fields w underscore while all are available as fields wo underscore (why is that so?), hence custom fields seems to map to frontend fields wo underscore if fields w underscore are not available. It should be either all fields are mapped to fields wo underscore or w underscore. For now, populating a field wo underscore seems to be also populating the corresponding field w underscore if available and vice versa, which will be displayed on the design if is inserted. Please advise the default behaviour of mapping a custom field should be to the field wo underscore or w underscore. There is no operational challenge at the moment however we would like to be assured by Accredible that there will not be any potential risk of impacting the existing mapping or at least be pre-empted with an alternative solution should there be related feature changes in future.