Not quite the case on the last point. It does propagate from a single entry of a transaction.
With the option checked, you enter the numbers in the Action field of *each* split and you can do this all in one entry from one register. (the option locks the actual NUM field against editing) But when you view one of the other registers, the corresponding transaction will have *its* number in the NUM field instead of any of the others. So if you enter a payment on a bill and use your check number on the payment split for the Checking register, then enter perhaps a sequential number on the AP split, when you view the Checking register you’ll see the check number in the NUM field, but in the AP register you’ll see the sequential transaction number there. (If you are in Transaction Journal view so you can see all splits, you’ll be able to see that check number in the Action field even from the AP register) Although I don’t currently use this option, I may switch. I use the NUM field for a time stamp since GnuCash (while keeping it internally) doesn’t let me set a time in addition to the date for a transaction. This can result in erroneous negative balances, particularly where it is impossible to have a negative balance, like a Cash account. My current method is to enter 24 hour time, without a “:” separator but ending in “t” to denote it is not a regular transaction number—e.g., 1514t for 3:14pm. When a customer pays me however with a check, that means I can’t enter the check number in that field and have to place it somewhere else. With this option checked, I could continue to use NUM for time stamps where I need to, and also record actual document numbers for the other register(s) in the transaction. Regards, Adrien > On Sep 17, 2018, at 9:00 AM, Paul Kinzelman <p...@kinzelman.com> wrote: > > Wow, I did not get that out of what I read at all. > It'd be very useful for people I think if you updated the documentation > to say that. > > So would a good summary be that if the box is unchecked, if you fill in > the number field in a transaction, it automagically propagates > to the other corresponding account register to keep them in sync. > > If the box is checked, you have to fill in the numbers in both places > manually (if you don't, the other one will be blank), > which allows them to be different. > > On 9/16/2018 10:59 PM, Adrien Monteleone wrote: >> Think of the option as more like either you have numbers for transactions, >> or you have numbers for splits. >> >> With the option unset, a payment transaction for example will have the same >> number both in the asset/liability register used to make/accept the payment >> and in the AP/AR register. >> >> With the option set, you could have different numbers depending on which >> register you are viewing. >> >> This might be useful in some cases to keep paperwork in sync. Your internal >> paperwork might use one number for a transaction but the external entity >> might use a different one. The option allows you to record both AND see each >> number in its proper perspective and context in your books. >> >> Regards, >> Adrien >> >>> On Sep 16, 2018, at 10:07 PM, Paul Kinzelman <p...@kinzelman.com> wrote: >>> >>> I read the docs and don't really understand the "Use split Action field for >>> Number" purpose. >>> It sounds like the Action field is moved to the Num field, and the Num is >>> hidden >>> someplace else? And it's inaccessible? >>> >>> Too bad the empty space can't be used for tag, that sounds like a great >>> solution. >>> I'm surprised that it can't be. >>> >>> However, it sounds like I can use the "Action" field for the Tag, and I >>> understand that I have to be careful to make sure the spelling is correct. >>> As long as I don't collide with one of the already populated items, seems >>> like I should be OK. >>> >>> Thanks! >>> >>> On 9/16/2018 10:24 AM, John Ralls wrote: >>>> But don’t confuse an empty space on the grid for a field. There’s no “tag” >>>> field, and adding one is complicated. >>>> >>>> There are already five free text fields in GnuCash, all searchable: >>>> Number, Description and Notes are part of transactions, Action and Memo >>>> are part of splits. Action is a little weird in that it’s a combo >>>> pre-populated with some values associated with certain GnuCash features so >>>> using it as a class/tag/subcategory might require extra effort and might >>>> interfere with a feature that uses it. >>>> >>>> There’s also the “Use split Action Field for Number” book option that >>>> displays the register account split’s action field in the Num column of >>>> the register, making the Number field inaccessible from the GUI. >>>> >>>> Since the fields are free text it requires user discipline to use any of >>>> them for categorization: One must be careful to always spell the values >>>> the same. Many users who want tags complain that that makes it too hard to >>>> use free text fields for categorization, but a tweak to the Action combo >>>> so that all previous entries for an action in splits for a particular >>>> account are added to the list part or using a similar combo in the Memo >>>> would go a long way to resolving that objection. >>>> >>>> Regards, >>>> John Ralls >>>> >>>>> On Sep 16, 2018, at 8:19 AM, Derek Atkins <de...@ihtfp.com> wrote: >>>>> >>>>> Search the list archives for "Tags". >>>>> SIt's an oft requested feature. >>>>> Patches welcome. >>>>> >>>>> -derek >>>>> Sent using my mobile device. Please excuse any typos. >>>>> On September 16, 2018 10:34:53 AM Paul Kinzelman <p...@kinzelman.com> >>>>> wrote: >>>>> >>>>>> Quicken normally specifies transactions into Categories for filtering >>>>>> for reports and such. >>>>>> >>>>>> But it also has a nice feature to allow a user to sort on a second field >>>>>> called 'Class' which can be specified for each transaction. >>>>>> >>>>>> Gnucash has what appears to be an unused field which could be >>>>>> used for the same purpose. If you view "Double Line", there's a >>>>>> space to the right of the "Notes" field which currently can't be >>>>>> used. >>>>>> >>>>>> Has anybody suggested or thought about using the unused field >>>>>> for this extra filtering purpose? >>>>>> >>>>>> _______________________________________________ >>>>>> gnucash-user mailing list >>>>>> gnucash-user@gnucash.org >>>>>> To update your subscription preferences or to unsubscribe: >>>>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user >>>>>> If you are using Nabble or Gmane, please see >>>>>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. >>>>>> ----- >>>>>> Please remember to CC this list on all your replies. >>>>>> You can do this by using Reply-To-List or Reply-All. >>>>> >>>>> _______________________________________________ >>>>> gnucash-user mailing list >>>>> gnucash-user@gnucash.org >>>>> To update your subscription preferences or to unsubscribe: >>>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user >>>>> If you are using Nabble or Gmane, please see >>>>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. >>>>> ----- >>>>> Please remember to CC this list on all your replies. >>>>> You can do this by using Reply-To-List or Reply-All. >>> _______________________________________________ >>> gnucash-user mailing list >>> gnucash-user@gnucash.org >>> To update your subscription preferences or to unsubscribe: >>> https://lists.gnucash.org/mailman/listinfo/gnucash-user >>> If you are using Nabble or Gmane, please see >>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. >>> ----- >>> Please remember to CC this list on all your replies. >>> You can do this by using Reply-To-List or Reply-All. >> >> _______________________________________________ >> gnucash-user mailing list >> gnucash-user@gnucash.org >> To update your subscription preferences or to unsubscribe: >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> If you are using Nabble or Gmane, please see >> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. >> ----- >> Please remember to CC this list on all your replies. >> You can do this by using Reply-To-List or Reply-All. > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
