Apparently, not all the fields in the database for tasks are exposed in the import process...
I am trying to import from a CSV file and one of the fields is due date. While the due date is clearly shown in the task editing form, there does not seem to be a way to import that date into EPIM. So, as a result, all my tasks have NO due date. That, obviously, is not acceptable.
Am I missing something here?
BTW, I did a test export of a task from EPIM and Due Date is not there. Due Time IS there, but not the date, and that, for me, is the critical field.
BTW2: Using trial of EPIM Pro 8.66.1 on Win10-64, 32 GB RAM, tons of hard drive space, i7 processor
Not all database fields
Moderators: TerryRogers, Max
-
- Guru
- Posts: 194
- Joined: Mon Dec 30, 2013 12:33 am
- Has thanked: 2 times
- Been thanked: 9 times
Not all database fields
I measure a good day by how little I fell behind.
Quick! Hire a teenager while they still know everything!
Quick! Hire a teenager while they still know everything!
-
- Site Admin
- Posts: 21714
- Joined: Wed Dec 08, 2004 11:39 pm
- Has thanked: 819 times
- Been thanked: 364 times
- Contact:
Re: Not all database fields
I suppose you are importing Tasks from CSV. Please see attached screenshot, of how you can define to import Due Date.
Maxim,
EPIM Team
EPIM Team
-
- Guru
- Posts: 194
- Joined: Mon Dec 30, 2013 12:33 am
- Has thanked: 2 times
- Been thanked: 9 times
Re: Not all database fields
Yes. I see how to define the field. But I would like it to appear in the field in the form. I tried defining the field during import, but then I end up with two "Due date" fields, one in the form and one in the custom fields. That's not good.
Why is the "native" due date field not exposed in the import dialog?
Why is the "native" due date field not exposed in the import dialog?
I measure a good day by how little I fell behind.
Quick! Hire a teenager while they still know everything!
Quick! Hire a teenager while they still know everything!
-
- Guru
- Posts: 194
- Joined: Mon Dec 30, 2013 12:33 am
- Has thanked: 2 times
- Been thanked: 9 times
Re: Not all database fields
Thanks, Max...
In fact, all fields exposed in ANY form should be mappable during import. That will result in fewer custom fields and more functionality/usability for the forms.
Is there any way to bulk move data from one field to another? If that were possible, I could do the importing now, creating a custom field, and then move that data in to the native field. The original versions of ACT! had that feature and it was terrific. (Please tell me if I'm not being clear.)
I'm going to have to wait until this fix is complete before I purchase. It's disappointing, but necessary for me.
In fact, all fields exposed in ANY form should be mappable during import. That will result in fewer custom fields and more functionality/usability for the forms.
Is there any way to bulk move data from one field to another? If that were possible, I could do the importing now, creating a custom field, and then move that data in to the native field. The original versions of ACT! had that feature and it was terrific. (Please tell me if I'm not being clear.)
I'm going to have to wait until this fix is complete before I purchase. It's disappointing, but necessary for me.
I measure a good day by how little I fell behind.
Quick! Hire a teenager while they still know everything!
Quick! Hire a teenager while they still know everything!
-
- Site Admin
- Posts: 21714
- Joined: Wed Dec 08, 2004 11:39 pm
- Has thanked: 819 times
- Been thanked: 364 times
- Contact:
Re: Not all database fields
There is no way to bulk-move data from one field to another.
A workaround would be to convert your data to iCal file (if CSV -> iCal converters exist) and use it to import to EPIM.
A workaround would be to convert your data to iCal file (if CSV -> iCal converters exist) and use it to import to EPIM.
Maxim,
EPIM Team
EPIM Team
-
- Guru
- Posts: 194
- Joined: Mon Dec 30, 2013 12:33 am
- Has thanked: 2 times
- Been thanked: 9 times
Re: Not all database fields
Thanks, Max...
A cumbersome workaround, but it will probably work.
I'd like to suggest that you have the bulk move function added as a feature. Very convenient, especially in view of problems with importing...
Stay well and safe...
A cumbersome workaround, but it will probably work.
I'd like to suggest that you have the bulk move function added as a feature. Very convenient, especially in view of problems with importing...
Stay well and safe...
I measure a good day by how little I fell behind.
Quick! Hire a teenager while they still know everything!
Quick! Hire a teenager while they still know everything!
-
- Guru
- Posts: 194
- Joined: Mon Dec 30, 2013 12:33 am
- Has thanked: 2 times
- Been thanked: 9 times
Re: Not all database fields
Has this issue been fixed? I'd really like to purchase, but can't even continue my evaluation of the product until this import issue is fixed.
thanks...and stay safe...
thanks...and stay safe...
I measure a good day by how little I fell behind.
Quick! Hire a teenager while they still know everything!
Quick! Hire a teenager while they still know everything!
-
- Site Admin
- Posts: 15601
- Joined: Thu Nov 25, 2004 3:12 am
- Has thanked: 1411 times
- Been thanked: 984 times
Re: Not all database fields
It should be working fine. Just make sure you select correct date/time format for importing to the Due Date column.
Android version of EssentialPIM. Keep all your data in sync!