Warnings are just warnings. We don’t care if you don’t.
A warning means there could be a problem somewhere. We are not sure. It may not be a big deal, but something did not import perfectly. The data still imported, but there were some problems with some of the fields/columns.
For example, you imported contact data and on the phone type you labeled something as "cell phone". If "cell phone" does not exist in your code management then this record will generate a warning. Is this a big deal? Not really. Should you fix it? Probably. But things are going to work just fine if you don't.
On the other hand, if you provide student data like "language fluency" and you pass in a code that does not exist. Is this a big deal? Yes. This is a problem that should be resolved because the data matters. If you hope to generate any language fluency reporting, then this data should be fixed.
Generally all data "matters" ... but we all agree that some data just matters more.
If we warn you on a field you don’t care about, don’t worry about it!
So how do you fix warnings?
Most of the time warnings are issues where the data that you are importing does not align to the data in your code tables. You have three options:
- Take a look at your code tables (Admin > Code Management) and make sure that the data that you are providing aligns to the codes in your code tables. You may need to change codes or add codes to resolve things here.
- Add some transformations to your data imports. Maybe you are sending us "00" in your data but you need it to say "0" when it imports. You can add a transformation (Admin > Core Data Configurations) to strip leading zeros, find and replace values, etc.
- Make changes to your data. Illuminate can't help you here. But if you have queries that are generating the data that you are importing, you can make changes to those data extraction queries as needed. This should probably be your last option.
For option 1 or 2 above, feel free to contact Illuminate support in order to get some direction on how to do this!