exporting selected account subtree

[TMaynard]

Thankyou Neil for the comprehensive responses to this multifaceted set 
of problems. I realize what you are tackling will open doors for a lot 
of new features for Gnucash, and I  only partially understand the 
implications.  I have snipped parts of  your responses and I  realize I 
should add one more qualifier for the kind of maneuver that could be 
supported earlier  in the list of incoming features. I am going to add 
to the A and B restrictions already stated:

    C: the export and graft is *one way* only  (big warning, never any 
re-import or return graft)
   
 This is the essence of labor saving import  of bank transactions. I 
know those tranactions belong in my COA and, once loaded as dummies, the 
tools are there to assign account labels. Thankfully the bank doesnt 
have to be concerned with ever receiving return data or to be concerned 
with a unique identifier or reimportation problem.   Similarly, if a 
business COA incorporates  a batch of transaction values for a few  
months of  business related transactions occurring in a personal account 
, those *copied*  tranactions  will not need to be exported back to the 
personal COA.  
   This seems important to enable  between certain "consenting" gnucash 
COA's.  I hope this type of restricted graft can be a high priority and 
maybe such a tool can be the venue for  some of the first look and feel 
additions.   Neil has used the metaphor of "collisions" and I  see that 
he really is constructing a coordinated traffic light system for the 
whole city. In the mean time some of the traffic could carefully turn 
Right on Red (with the warning that they should know where they want to 
go and they can't return someday with a different cargo.)
 Thanks,
Rusty
   
Neil Williams wrote:

>On Tuesday 01 March 2005 9:43 pm, TMaynard wrote:
>  
>
>
>  
>
>> I would welcome a beta testing  tool to do :
>> A:  export (*copy*) subtree from source COA
>>B:  graft new (under *empty* placeholder) in destination COA.
>>    
>>
>  
>
>>At some point the incoming bank transactions are assigned unique QUID's
>>and dummy or one sided  account labels.
>>    
>>
>
>That's your basic problem, right there. Without retaining the GUID, it becomes 
>hit or miss when you re-import that data - you cannot be absolutely sure that 
>the incoming data really does match existing data unless the GUID is retained 
>through export AND import.
>
>  
>
>> I would even welcome a blow by blow description of how to safely
>>identify&copy the pertinent subtree of the source COA and paste *only*
>>under/within  the waiting "placeholder" in the destination XML.
>>    
>>
>
>I'll look at that. The test case CoA export will provide the XML and it should 
>be relatively easy to identify the relevant accounts.
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>gnucash-user mailing list
>gnucash-user at gnucash.org
>https://lists.gnucash.org/mailman/listinfo/gnucash-user
>  
>