I am only studying Mendix for a week now, and I am not even a programmer, and may be that's why it took be several hours to find out the answer to this question. I believe above it remains unanswered, so here is what I found when running in this error importing my first Excel files with the Excel Importer: 'Invalid byte 2 of 2-byte UTF-8 sequence'. Normally you get this message when your file isn't UTF-8 or has an invalid special character. But here it is something else: In the Import_Overview page you should not use the tab Import Template, but Import File. Sounds logical, or what? However, I am not the only one who made the mistake, I am sure of that, because there are several questions about this error on this forum. You can find the answer on the forum as well, but almost hidden under this question: Excel importer - Error, need help debugging.
Tim,
Just resync the model reflection and try the import again. Make sure the correct modules are set for syncing.
You could implement such a validation in a Java action:
Also have a look at the ASuCheckModelAndTemplates After Startup microflow in the _USEME folder. This microflow syncs the domain model every time you start the application and performs a check between the configured templates and the current domain model. Any non existing columns are automatically set to ignored.
I remember putting in a feature request for an api call that would return the database schema version. This is actually stored in a metadata table and would be perfect to know if you ened to sync MxModelReflection automatically on startup. No idea what happened to it.
What we do is sync on startup everytime when running on a server, but not on a development machine, as it takes pretty long to do.
Sorry I don't know the rules of the forum but did any of these answers work for you Tim? I have the same problem.