No validation of fields on importing custom module data

I inadvertently discovered that importing an excel file of custom module data does not do any form of field matching so when you import the data for a custom module for one client into another client’s custom module, Treepl quite happily imports the data to the wrong data file and client without a care in the world.

Surely we should have the import checking for a match on field names provided in row 1 of the import file against the custom module you are importing into?

Hi @TopLeftDesigns ,
This feature is being discussed among the team, but to speed up this process, please post your requests on Treepl forum under Public Backlog category.

1 Like