Quicken 2013 and Mobile App Syncing Strips-off Split Transactions, etc...
Hello
I love the idea of Quicken Mobile and have been using the app on both my iPad and iPhone for a few days. Everything seems to be working and syncing fine except for:
1) it seems the Mobile App will not recognize split transactions when synced from the desktop Quicken 2013
2) and more troubling, not only will the Mobile App not recognized split transactions but the mobile app when synced to desktop Quicken will then strip-out all split transactions from desktop Quicken and replace the split transactions with a single transaction category of "uncategorized" on desktop Quicken.
3) it seems the Mobile app is creating two events in the registered for a single event in the desktop Quicken.
4) There doesn't seem a way to create a split transaction in the Mobile App.
I'm wondering if others are seeing similar problems as I am recording.
I have the current version of Quicken 2013 installed (R2).
Cheers
Craig
I love the idea of Quicken Mobile and have been using the app on both my iPad and iPhone for a few days. Everything seems to be working and syncing fine except for:
1) it seems the Mobile App will not recognize split transactions when synced from the desktop Quicken 2013
2) and more troubling, not only will the Mobile App not recognized split transactions but the mobile app when synced to desktop Quicken will then strip-out all split transactions from desktop Quicken and replace the split transactions with a single transaction category of "uncategorized" on desktop Quicken.
3) it seems the Mobile app is creating two events in the registered for a single event in the desktop Quicken.
4) There doesn't seem a way to create a split transaction in the Mobile App.
I'm wondering if others are seeing similar problems as I am recording.
I have the current version of Quicken 2013 installed (R2).
Cheers
Craig
0

Comments
Is there not a way to prevent the unassuming customer from syncing their data and unknowingly loosing data? Most people can understand and deal with bugs here and there but not bugs that cause a data loss. It is expected for beta testers to be extra careful with their data and have a means of rolling back to an earlier date but many users of quicken may not pay enough attention to their data to recognize the problems that are being caused by quicken sync and will have lost data with no easy way to roll back. Please, find a way to disable the feature if nothing else until you have a suitable fix. Or even put up one of those notices that tell about upgrades but have it talk about not activating quicken sync until further notice. DATA LOSS HAS TO BE STOPPED!
Daaknes
As a Quicken 2013 beta tester and fellow Quicken user, I am in hopes that all those that read this post that have suffered data loss, inconvenience, etc. (there are many) as a result of using Sync to Cloud will "take a break" in your recovery process and surf over to amazon.com and post exactly what happened to you in an amazon.com review of Quicken Deluxe or whatever version of Quicken 2013 you purchased. You need not have purchased Quicken 2013 from amazon to comment in a review there. Let others know what happened to you as a direct result of Intuit knowingly and with little concern for the end user, releasing a feature (Syn to Cloud) that was not properly tested and was know to be problematic throughout beta testing and well before Sept. 30th when Quicken 2013 was made available at the retail level. Thanks for taking the time to get the word out to others before they suffer data loss, inconvenience, etc.. Your Quicken 2013 review at amazon.com will surely prevent others from going through what you have gone through.
What really chaps my rear is that Quicken Tamara is still telling people how to download the app but not mentioning any of the issues that have cropped up.
Prime example:
https://qlc.intuit.com/post/show_full/czJioCej0r4QXMeJfaade6/how-do-i-syn-my-phone-and-ipad-to-2013-qucken?ppid=149434242
-----------------------------------------------
Initial post: Oct 7, 2012 6:49:07 PM PDT
Ken says:
(MANUFACTURER)
Hi Darrin,
I am sorry to hear you are having problems. I am responsible for the development of Quicken and want to assure you we are working on sync issues that some of our customers, including you, are experiencing. Can you check if you are running at least R2. On one of our sites, we incorrectly distributed a release 21.1.1.12 that wouldn't update. This can be fixed by following this FAQ (http://knowledgebase.quicken.com/support/help/quicken-2013-error-7-during-install/SLN64047.html). We are also updating our auto-patch this evening such that this particular problem will be fixed by installing the update.
If you are on R2 and still having problems with sync, please contact me at [email protected] with additional details to the problems you are seeing. We are committed to resolving any sync related issues ASAP. I am personally following through on these issues to get them resolved. This does work for the majority of our customers and we are trying to get it fixed for those who it is not working. Again, I am sorry for the inconvenience.
Acknowledging that Sync to Cloud is deleting transactions and split lines!! (another words data loss if you dare Sync to Cloud with Quicken 2013)
Many here to include some beta testers of Quicken 2013, have pressed for days now for Intuit to do the right thing and start notifying / warning the purchasers of Quicken 2013 in regard to this issue. Well, 8+ days it took and unfortunately, hundreds (thousands?) of users have lost data as they were unaware of the issue/ not made aware of this issue by Intuit.
Here is the containment article ( just posted, PM 9/8/12) it is about time Intuit) that Intuit it has released/posted under duress it seems / because they were pressured to do the right thing:
http://knowledgebase.quicken.com/support/help/quicken-2013-mobile-sync-deletes-data/SLN64122.html
It is ridiculous that I am reading a thread that proves that Intuit has known about this disastrous problem for over 6 months. Not only did this issue just destroy nearly a hundred hours of my work it also made my federal tax filing incorrect. WTF? Pull this junk code off the market until it works and is GUARANTEED not to damage data on the host computer. This willful negligence is a class action lawsuit waiting to happen.
NOTE to others who may read this Comment: This is a special case scenario, offered ONLY to magicd0n. Any other requests received will not receive a response. Once a solution has been found and presented to magicd0n, an answer will be provided directly to him and a more generic answer will be posted back here. Once I've received the information from magicd0n, I'll remove the contact information from this Comment.