View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002832||1 - Backlog||Enhancement||public||2018-08-09 10:42||2018-08-09 10:42|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0002832: Importing Custom Fields on Lookup|
|Description||I can not verify or replicate this issue, so I entered it as an Enhancement request. I have one customer who claims HRD use to import the "Custom" which were populated with data in a previously logged QSO, into the Logbook ALE when that same contact was logged at a later date and the lookup was done.|
I have tested this on the current version (220.127.116.113) and on a couple of the versions the customer claimed worked, and on my tests on a VM, none of the versions would import the Custom fields into the ALE, even when I had only the Logbook and Country list selected as the methods used for Lookup.
What this enhancement would do is, when a contact has been logged in the logbook, with Data populated in the Custom Fields of the ALE at the time of logging and saved in the logbook if that contact was worked at a later date and a the lookup when the callsign was entered imports the data from the logbook to populate the ALE, they would like to have the Custom fields also imported into the ALE and when that contact is saved again, all the same data in the Custom fields would be saved to the new record.
|Additional Information||Ticket #156520 - First ticket to report this issue|
Ticket #660517 - This ticked reported the fact that in 18.104.22.1683 does NOT import the custom fields from previously logged contacts into the ALE if that same contact is entered in the ALE and a lookup done. He didn't claim it was working in a previous version and understands the difference might be he is running HRD on an IMac computer using Parallels and that under this type of environment the HRD software may just look or perform a bit differently.
|Tags||No tags attached.|