I am running Jtrac 2.3.0 trying to import an xls file into a new space but am getting the error "Field has to be mapped: {0}". I have created the space and created space fields but for some reason the error still comes up when trying to Import into Selected Space. Any help is appreciated thank you
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I haven't used the Excel import, but a quick reading of the source code indicates that at least 4 columns must be present, otherwise that error message is shown: summary, detail, loggedBy and assignedTo. Do you have those 4 columns? Make sure that there is no white space before or after those names.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the late reply, I found the file has to be specifically a .xls file .xlsx will not work. It seems to crash quite a bit so I've been struggling with time to work on it but I did try this with 4 columns. Maybe there is an easier way to import data.. I do have a .bak file from a mysql backup if that would make the process easier.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah yes, I had generalized the Excel file handling to accommodate XLSX as well as XLS, but that's only in the source code so far, not in the released version.
Hello, I have just installed a new Jtrac 2.3.1 for a client and am having issues importing a .xls file into Jtrac. I have rebuilt their space exactly as it was originally built and still cannot import the file. I get the same "Field has to be mapped: {0}" 4 times every time I try to import. I had to rename the exported .xls Collumn headers in order to get it opened by the new Jtrac. The old Jtrac was version 2.1.0. I do not have a detail collumn and would prefer not to have to add one as this is exactly how the client wants it and uses it. I would appreciate any help! Thank you for your time.
I have re-exported my DB to include the detail column but I still have the same error upon attempting to import. Do the 4 required columns have to be named exactly those names or are there some form of regular expression, or something similar, to handle variations in the exact column name EG: Resolving "Logged By" to "loggedBy" for that field and other fields which contain spaces? Because now that I have the 4 required fields and it's still failing to import I am unsure of what exactly is the root cause of this behavior is.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The error message somehow doesn't display which field names are missing,
but there are exactly 4 required fields: summary, detail, loggedBy, and
assignedTo. They need to be written exactly as I posted them here. So no,
there's no mapping of any kind going on. There isn't a lot of documentation
for this, but check out https://www.youtube.com/watch?v=T6GxZn4gNYM
I have re-exported my DB to include the detail column but I still have the
same error upon attempting to import. Do the 4 required columns have to be
named exactly those names or are there some form of regular expression, or
something similar, to handle variations in the exact column name EG:
Resolving "Logged By" to "loggedBy" for that field and other fields which
contain spaces? Because now that I have the 4 required fields and it's
still failing to import I am unsure of what exactly is the root cause of
this behavior is.
I'm just playing around with the Excel import, and it seems to have other
issues as well. I have yet to import a file successfully, so I can't say
for certain that it currently works at all. I'll keep looking at that over
the next few days, and will post here with what I find.
The error message somehow doesn't display which field names are missing,
but there are exactly 4 required fields: summary, detail, loggedBy, and
assignedTo. They need to be written exactly as I posted them here. So no,
there's no mapping of any kind going on. There isn't a lot of documentation
for this, but check out https://www.youtube.com/watch?v=T6GxZn4gNYM
On Thu, Jun 15, 2023 at 2:43 AM Josh Nerland
jnerland@users.sourceforge.net
wrote:
I have re-exported my DB to include the detail column but I still have the
same error upon attempting to import. Do the 4 required columns have to be
named exactly those names or are there some form of regular expression, or
something similar, to handle variations in the exact column name EG:
Resolving "Logged By" to "loggedBy" for that field and other fields which
contain spaces? Because now that I have the 4 required fields and it's
still failing to import I am unsure of what exactly is the root cause of
this behavior is.
Playing around with the Excel some more, it's actually better than I initially thought. The column names do not have to be exactly as I said above, but the space they're to be imported into needs to have at least fields that correspond to those. If the names are different, then they need to be mapped before import. And the users in the loggedBy and assignedTo fields need to be mapped manually before the import will work. But then it works OK.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running Jtrac 2.3.0 trying to import an xls file into a new space but am getting the error "Field has to be mapped: {0}". I have created the space and created space fields but for some reason the error still comes up when trying to Import into Selected Space. Any help is appreciated thank you
I haven't used the Excel import, but a quick reading of the source code indicates that at least 4 columns must be present, otherwise that error message is shown: summary, detail, loggedBy and assignedTo. Do you have those 4 columns? Make sure that there is no white space before or after those names.
Sorry for the late reply, I found the file has to be specifically a .xls file .xlsx will not work. It seems to crash quite a bit so I've been struggling with time to work on it but I did try this with 4 columns. Maybe there is an easier way to import data.. I do have a .bak file from a mysql backup if that would make the process easier.
Ah yes, I had generalized the Excel file handling to accommodate XLSX as well as XLS, but that's only in the source code so far, not in the released version.
Can you share the file you're trying imported with me? Feel free to edit to remove sensitive data. My email can be found at https://www.ulfdittmer.com/images/email.jpg
Hello, I have just installed a new Jtrac 2.3.1 for a client and am having issues importing a .xls file into Jtrac. I have rebuilt their space exactly as it was originally built and still cannot import the file. I get the same "Field has to be mapped: {0}" 4 times every time I try to import. I had to rename the exported .xls Collumn headers in order to get it opened by the new Jtrac. The old Jtrac was version 2.1.0. I do not have a detail collumn and would prefer not to have to add one as this is exactly how the client wants it and uses it. I would appreciate any help! Thank you for your time.
I have re-exported my DB to include the detail column but I still have the same error upon attempting to import. Do the 4 required columns have to be named exactly those names or are there some form of regular expression, or something similar, to handle variations in the exact column name EG: Resolving "Logged By" to "loggedBy" for that field and other fields which contain spaces? Because now that I have the 4 required fields and it's still failing to import I am unsure of what exactly is the root cause of this behavior is.
The error message somehow doesn't display which field names are missing,
but there are exactly 4 required fields: summary, detail, loggedBy, and
assignedTo. They need to be written exactly as I posted them here. So no,
there's no mapping of any kind going on. There isn't a lot of documentation
for this, but check out https://www.youtube.com/watch?v=T6GxZn4gNYM
On Thu, Jun 15, 2023 at 2:43 AM Josh Nerland jnerland@users.sourceforge.net
wrote:
I'm just playing around with the Excel import, and it seems to have other
issues as well. I have yet to import a file successfully, so I can't say
for certain that it currently works at all. I'll keep looking at that over
the next few days, and will post here with what I find.
On Thu, Jun 15, 2023 at 3:47 PM Ulf Dittmer udittmer@users.sourceforge.net
wrote:
Playing around with the Excel some more, it's actually better than I initially thought. The column names do not have to be exactly as I said above, but the space they're to be imported into needs to have at least fields that correspond to those. If the names are different, then they need to be mapped before import. And the users in the loggedBy and assignedTo fields need to be mapped manually before the import will work. But then it works OK.