Menu

#348 Repeat transactions created x days early.

1.0.1.0
closed-wont-fix
nobody
5
2015-02-24
2014-12-12
ukuser
No

Hi,

It would be really useful if repeat/scheduled transactions could be created x days before they are scheduled for. I would find this useful for cashflow being able to see when transactions happen for the next 30 days.

Thanks.

Related

Feature Requests: #348

Discussion

  • Richard Ely-Harris

    This feature definitely gets a vote from me - it would be so useful. Thank you.

     
  • Stefano

    Stefano - 2015-01-11

    This feature has now been implemented as follows:

    The Repeating Transactions dialog's Next Occurrence control has been replaced with Due Date. Payment Date is shown in the transaction.

    The calendar control sets both of these, and allows Due Date to be set to an advanced date. Setting this to a previous date will be reset to Payment Date when saved.

    When the payment date arrives, the home page will display 0 days delay!

    In auto mode, payment will be activated on start up.
    In semi auto mode, it will prompt payment.

    If the payment dialog is cancelled, it will prompt on next session. (Normal behaviour.) If this is done for several days, the home page will display x days delay! until the due date where it will show x days overdue!

    Ref: https://github.com/moneymanagerex/moneymanagerex/pull/346

    This feature will be available on next release very soon.

     
    • Pat O

      Pat O - 2015-01-12

      Just to check, if the db is opened in a previous version of MMEX, will it
      behave properly or is is not backwards compatible once created in the new
      version?

      On Sunday, January 11, 2015, Stefano stef145g@users.sf.net wrote:

      This feature has now been implemented as follows:

      The Repeating Transactions dialog's Next Occurrence control has been
      replaced with Due Date. Payment Date is shown in the transaction.

      The calendar control sets both of these, and allows Due Date to be set
      to an advanced date. Setting this to a previous date will be reset to Payment
      Date
      when saved.

      When the payment date arrives, the home page will display 0 days delay!

      In auto mode, payment will be activated on start up.
      In semi auto mode, it will prompt payment.

      If the payment dialog is cancelled, it will prompt on next session.
      (Normal behaviour.) If this is done for several days, the home page will
      display x days delay! until the due date where it will show x days
      overdue!

      Ref: https://github.com/moneymanagerex/moneymanagerex/pull/346

      This feature will be available on next release very soon.

      Status: open
      Group: 1.0.1.0
      Labels: Repeating Transactions
      Created: Fri Dec 12, 2014 07:11 PM UTC by ukuser
      Last Updated: Sun Jan 11, 2015 07:19 PM UTC
      Owner: nobody

      Hi,

      It would be really useful if repeat/scheduled transactions could be
      created x days before they are scheduled for. I would find this useful for
      cashflow being able to see when transactions happen for the next 30 days.

      Thanks.

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/moneymanagerex/feature-requests/348/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Feature Requests: #348

  • Stefano

    Stefano - 2015-01-12

    To answer the question, the database is fully backward compatible.
    Going forward again could cause what seems to be a bug, which was fixed by the database upgrade mechanism.

    The technical stuff:

    Dialog and Display Modification
    - Names changed to reflect the change
    - Small change in appearance and behaviour to accommodate the new Due Date

    Database version 2:
    The Bill_Deposits table has 2 date storage places.
    - next_occurrence - Stores the date of next occurrence
    - transdate - Not used but is initialised when the transaction is first created.

    Entering a transaction,
    The date of next occurrence is advanced but transdate is not.
    next occurrence date is used to determine when a transaction is overdue.

    Database version 3
    - next_occurrence - Stores the date of next occurrence or Payment Date (No real Change)
    - transdate - Now used to store the Due Date

    Entering a transaction,
    The date of next occurrence and transdate is advanced to the new date.
    Transdate is now used to determine when a transaction is overdue.

    Problems between old and new versions
    With transdate being set to some time in the past, all payments within 14 days would show up as being overdue, and could be misinterpreted as a bug. To correct this problem from occurring, database version control was utilised. (Was already in existence)

    Database Version Control
    On initial startup of a database at version 2,
    1. The Bill Deposits table is modified by setting transdate the same as next_occurance_date
    2.The database version counter is changed from 2 to 3

    Point 2 has the effect of preventing any subsequent modifications to the table.

    Using an previous version of MMEX
    No change, except possible loss of new feature if it is set up.

    Using the new version of MMEX on an updated database
    This could re-introduce the initial problem that the version control was designed to fix.
    This would only occur if or when a transaction is entered by an older MMEX version.

    To correct this, every repeat transaction may require resetting by editing the transaction to reset transdate as the Due Date.

    I hope this explains what the change is and how it affects the database.

     
  • Nikolay

    Nikolay - 2015-02-24
    • status: open --> closed-wont-fix
     

Log in to post a comment.