(Canadian

Yes. I think that may be the best way to satisfy multiple users and their respective needs/desires. Hopefully that's a simple implementation.Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
Yes but the question becomes what action would be used to clear the account indicator?Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
Have not seen 4.4.1 yet? Is it still in process?Quicken Marcus said:Interesting idea. So if I'm understanding this request correctly, you want to have a key command to see the split pop-over instead of being forced to pop open the edit view.
As a complete aside, but just to highlight where I am coming from, although I would really like to see the re-introduction of the downloading and matching workflow mentioned above (as would MANY others), and then for this to work in tandem with the account indicator, this and other features discussed here are not features that will get me (and many other users) off of QM2007.Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
It is being released in stages...only 2000 downloads initially. Then if no new serious issues arise, it will be released to all users.Eagle22 said:Marcus,
Have not seen 4.4.1 yet? Is it still in progress?
It's getting close...if Cmd-Opt-S could also close a split and exit edit mode that would be helpful, especially if nothing has been changed...makes for a more consistent experience; not 2 different keystrokes, like in QM2007.Quicken Marcus said:Interesting idea. So if I'm understanding this request correctly, you want to have a key command to see the split pop-over instead of being forced to pop open the edit view.
Items 3, 1, 2 in this order very important to meNice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
Thanks smayer97 for raising the points about what it will take to clear the indicator. You've clearly been thinking through this and I appreciate your bringing that to bear here. I think I'd presumed that it would automatically disappear after the user had reviewed all the new/recently downloaded transactions. Could we put your options to a users vote or will that only muddy things further?Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
So now we have this conversation taking place in 2 places, here and on this thread too. Not sure where the best place to continue is, but on this thread I know that Marcus is currently reading the replies and comments.Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
@Snoopy FC I think part of defining options depends on what the short term and long term plans are for Quicken because if they do implement the option for the workflow mentioned (which I hope they eventually do at some point, and based on demand I believe it is warranted), this will have a bearing on what the best path should be from whatever solution is implemented in the short term to the needed solution in the long term. In other words, I suggest that there needs to be more info provided to come up with feasible options both for now and later.Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
Well said. I agree.Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
Also, I would say in the short term, I'd rather see a major addition like loan amortization added before this is addressed further. This new transaction processing piece is significant, but it seems the big elephant in the room is loan amortization, which has been a significant missing piece for a long time.Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
Prior to the update my Quicken Data File was stored in Documents
and backed up to Library/Application Support/Quicken 2017/Backups.
Following the update my Quicken Data File is still stored in
Documents BUT a new folder has appeared in Library/Application Support/Quicken
2017/Backups, called Automatic Backups, which contains a backup made each time I
quit. There is still an old backup file in the Backups folder.
Is this what is intended and are there any other backups
being created somewhere else?
You may want to add your vote to the following idea: https://getsatisfaction.com/quickencommunity/topics/add-ability-to-organize-reports-by-income-and-expense-vs-cash-flow-in-quicken-for-macGil said:How about adding a "Cash Flow" Report for monthly and a graph showing it over multiple months?
The old backup is when you must have performed a manual backup. The locations are the default locations. These are as intended. You can change the locations in your preferences if you choose.Pineman said:Sorry if I appear a bit thick but I'd like a bit of advice about the new backup facility.
Prior to the update my Quicken Data File was stored in Documents
and backed up to Library/Application Support/Quicken 2017/Backups.Following the update my Quicken Data File is still stored in
Documents BUT a new folder has appeared in Library/Application Support/Quicken
2017/Backups, called Automatic Backups, which contains a backup made each time I
quit. There is still an old backup file in the Backups folder.Is this what is intended and are there any other backups
being created somewhere else?
I suggest you read the following post about how you can add your vote for the features to improve customization of reports: https://getsatisfaction.com/quickencommunity/topics/does-quicken-for-mac-2017-have-an-income-stateme...Gil said:How about adding a "Cash Flow" Report for monthly and a graph showing it over multiple months?
I love the attention you are paying to this product!Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
You can add your VOTE to have Credit card balances reflected in Bill Reminders (dynamically update).Kevin said:I would like to see an option in Quicken Mac to use the current credit card balance for scheduled transfers from another account.
You can add your VOTE to Add Ability to Print List of Accounts and Balances.Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
Yes, this is how we designed it. We didn't want to accidentally delete a backup file that you created so we're putting the backups we're automatically creating in a separate folder. This way you know what files will be automatically deleted and maintained by Quicken. If you want to save off a backup every now and then you can simply copy one of these auto-backed up files and move it outside of the Automatic Backup folder so it won't get auto-replaced.Pineman said:Sorry if I appear a bit thick but I'd like a bit of advice about the new backup facility.
Prior to the update my Quicken Data File was stored in Documents
and backed up to Library/Application Support/Quicken 2017/Backups.Following the update my Quicken Data File is still stored in
Documents BUT a new folder has appeared in Library/Application Support/Quicken
2017/Backups, called Automatic Backups, which contains a backup made each time I
quit. There is still an old backup file in the Backups folder.Is this what is intended and are there any other backups
being created somewhere else?
I posted some comments in the other post. I don't think there's enough information to fully figure out the problem but I provided some places to investigate.RCinNJ said:Marcus, thank you for hosting this thread. I am going to lobby for my biggest problem. This has to do with how QM is not correctly keeping track of the Cash/Settlement/MMA fund in brokerage accounts (it is called different things, but is the source of money from which cash is added or removed when there are transactions in an account). From past and current posts it seems the problem goes back at least to QM2015 and has never been addressed. I assume this is not a problem with Quicken for Windows. My problem is at Vanguard.
I have posted on several threads including this one https://getsatisfaction.com/quickencommunity/topics/issues-adding-shares-in-quicken-for-mac-2016 which includes screen shots. Please read through this thread! Thank you!
4.4.1 is available to everyone now including Mac App Store customers.Eagle22 said:Marcus,
Have not seen 4.4.1 yet? Is it still in progress?
We've given this a lot of thought. Windows supports both the blue dots and the red flag. The red flag is tied to the comparative register feature and is what smeyer refers to. If you turn off the comparative register, Windows displays a blue dot. Since the Mac has never had the comparative register, the blue dot seemed like the natural feature to add first. Although we know many like the comparative register workflow where one must accept every transaction before it gets added to their register, we believe that many more people especially younger people find this work flow cumbersome. With that said, we know a lot of long time Quicken users like this work flow and so we will add the red flag type behavior that smeyer is promoting at some point.Nice new features. Great that these items are being addressed. I only wish they were implemented completely.
Auto-Backup: why could it not be implemented with the option to choose how many backup copies, like in QM2007?
New Transaction Account Sidebar Indicator: What is the criteria that makes the blue dot go away? Without that piece of information how are we to know what it means, if it is working correctly, or what the process is to manage or control it?
Preference to Turn Off Auto-Opening Splits: why could this not be implemented to control separately the behaviour when open a split vs when to close a split, like in QM2007, and how it was requested 3 1/2 months ago here: Expanding split transactions and detailed here?
I like some of these improvements but I would strongly suggest that when you implement a feature that has existed before, like in QM2007, that you make it at least as complete as the original, If you choose to improve on it and add more, that is great. But to deliver less than the original is simply frustrating! I can understand delivering a feature in multiple stages when it is more complex but I just do not see the reason for these partial implementations, especially if the feature is a small one.
smayer, I like your wording. That would work.Concordman said:Adding additional backups when no further data has been entered is not useful. Something to think about for future modifications:)