It should be possible for them to document this and escalate the case to the produce development team.
> (2) Contact Quicken Support by phone, and ask a support representative to screen share with you to walk through creating a new file from the Banktivity exported QIF to see that the data is not importing correctly. Unfortunately, if the person at Quicken validating the submissions cannot reproduce the problem - which they clearly can't without a current Banktivity data file - they may not investigate it further. You generally will not hear any response to such a bug report, except in rare cases whether they want to reach out for more information. > (1) Use the Help > Report a Problem to explain carefully that the import from Banktivity appears to be broken Include in your note that you'd be willing to provide a copy of your Banktivity file to help them with testing.
> I think your have two possible paths forward: Or if they are, they have decided not to invest resources into keeping up with such updates because their stats show relatively few people are using it. > On the Quicken end, my guess is they aren't constantly re-testing this import process, so if something has broken, they're likely not aware of it. (That could have been just keeping up with new features, or a minor tweak to fix a bug - or could have been to slow down defectors and stick it to Quicken to keep up.) Somewhere along the way, the folks at iBank/Banktivity made some change to the structure of their QIF export. > Here's my guess: Quicken wrote a converter for iBank years ago, and it worked. While I understand Quicken has no control over what Banktivity does, I feel that if they have a feature to import from Banktivity, then they should look into reports that something changed and that it's not working - or they should remove the claim that they can import from Banktivity if they have consciously decided not to pursue it. While I understand Quicken has no control over what Banktivity does, I feel that if they have a feature to import from Banktivity, then they should look into reports that something changed and that it's not working - or they should remove the claim that they can import from Banktivity if they have consciously decided not to pursue Here's my guess: Quicken wrote a converter for iBank years ago, and it worked. Unfortunately, some support reps may not go that extra mile, and may fall back on the reply from Quicken Anja that Quicken has no control over the QIF export and does not guarantee the results. (2) Contact Quicken Support by phone, and ask a support representative to screen share with you to walk through creating a new file from the Banktivity exported QIF to see that the data is not importing correctly. (1) Use the Help > Report a Problem to explain carefully that the import from Banktivity appears to be broken Include in your note that you'd be willing to provide a copy of your Banktivity file to help them with testing. I think you have two possible paths forward: On the Quicken end, my guess is they aren't constantly re-testing this import process, so if something has broken, they're likely not aware of it. Here's my guess: Quicken wrote a converter for iBank years ago, and it worked.
0 kommentar(er)
