@gnucash.org>>> On
>>>>>> Behalf Of Tom Olin via gnucash-user
>>>>>> Sent: Monday, July 3, 2023 1:55 PM
>>>>>> To: Kalpesh Patel mailto:kalpesh.pa...@usa.net>
>>>>>> <mailto:kalpesh.pa...@usa.ne
hange flag or some other thing to the data to prevent you
>> from exporting it as easy as it used to be. This could be the discrepancy
>> you are experiencing. In other words, to prevent people from doing what
>> you are exactly trying to do -- they may have placed a simple da
gave a one-year period where
>>>>> you could export data. While this may be a stretch, I believe that they
>>>>> may have somehow added a change flag or some other thing to the data to
>>>>> prevent you from exporting it as easy as
rectly and the next does not. Just my two cents -- for what it is worth
> ( which could be nothing at all!)
>
> Ken
>
> -Original Message-
> From: gnucash-user mailto:outlook@gnucash.org >> On Behalf Of
> Tom Olin via gnucash-user
> Sent: Monday, July 3, 2023 1
repancy you are experiencing. In other words, to prevent people from
>>>> doing what you are exactly trying to do -- they may have placed a simple
>>>> data offset or some other thing into the data to prevent easy export.
>>>> Again, this could be a stretch
data offset or some other thing into the data to prevent easy export.
>> > Again, this could be a stretch -- but it would explain why one year comes
>> > over correctly and the next does not. Just my two cents -- for what it is
>> > worth ( which co
t;>> not because they need yours.
>>> >
>>> >> On Jul 3, 2023, at 4:52 PM, Kalpesh Patel
>>> wrote:
>>> >>
>>> >> I am likely grasping straws here like David but did you verify the
>>> format of the date that it is
ts -- for what it is worth
>> ( which could be nothing at all!)
>> >
>> > Ken
>> >
>> > -Original Message-
>> > From: gnucash-user
>> On Behalf Of Tom Olin via gnucash-user
>> > Sent: Monday, July 3, 2023 1:55 PM
>> > To:
> correctly and the next does not. Just my two cents -- for what it is worth
> > ( which could be nothing at all!)
> >
> > Ken
> >
> > -Original Message-
> > From: gnucash-user > <mailto:outlook....@gnucash.org>> On Behalf Of Tom Olin via gnucash-
gnucash-user
> On Behalf Of Tom Olin via gnucash-user
> > Sent: Monday, July 3, 2023 1:55 PM
> > To: Kalpesh Patel
> > Cc: gnucash-user@gnucash.org
> > Subject: Re: [GNC] Importing data from QuickBooks Online
> >
> > Good shot, but no, date formats are consis
On
> Behalf Of Tom Olin via gnucash-user
> Sent: Monday, July 3, 2023 1:55 PM
> To: Kalpesh Patel
> Cc: gnucash-user@gnucash.org
> Subject: Re: [GNC] Importing data from QuickBooks Online
>
> Good shot, but no, date formats are consistent.
>
> --
> Tom
>
>
en
>
> -Original Message-
> From: gnucash-user On
> Behalf Of Tom Olin via gnucash-user
> Sent: Monday, July 3, 2023 1:55 PM
> To: Kalpesh Patel
> Cc: gnucash-user@gnucash.org
> Subject: Re: [GNC] Importing data from QuickBooks Online
>
> Good shot, but no, date f
: gnucash-user On
Behalf Of Tom Olin via gnucash-user
Sent: Monday, July 3, 2023 1:55 PM
To: Kalpesh Patel
Cc: gnucash-user@gnucash.org
Subject: Re: [GNC] Importing data from QuickBooks Online
Good shot, but no, date formats are consistent.
--
Tom
The federal government imposes a tax on you so YOU
To: Jean L
> Cc: gnucash-user@gnucash.org
> Subject: Re: [GNC] Importing data from QuickBooks Online
>
> Jean,
>
> Thanks for that. I did play with a few similar options but couldn’t get
> anything to work easily. Some were aimed more at Quicken or QuickBooks
> desk
, July 03, 2023 12:14 PM
To: Jean L
Cc: gnucash-user@gnucash.org
Subject: Re: [GNC] Importing data from QuickBooks Online
Jean,
Thanks for that. I did play with a few similar options but couldn’t get
anything to work easily. Some were aimed more at Quicken or QuickBooks desktop
instead
All records came from the same account tree at the same time.
We need more straws!!! :-)
--
Tom
How many dollars would you own if the federal government had balanced its
budget every year since the founding of our country? (Hint: It’s an exact
number.)
> On Jul 3, 2023, at 2:32 PM, David
Really grasping at straws now, but invisible characters/extra spaces in the
2022 account names?
--
Dave Reiser
dbrei...@icloud.com
> On Jul 3, 2023, at 12:29 PM, Tom Olin wrote:
>
> David,
>
> Both import files were generated from the same 2-year QBO export, so they
> have identical
David,
Both import files were generated from the same 2-year QBO export, so they have
identical structure. The process was:
QBO export -> convert to CVS -> my script -> unified import file (CVS)
The problem occurred identically whether I imported the unified file or just
the 2022 data
Jean,
Thanks for that. I did play with a few similar options but couldn’t get
anything to work easily. Some were aimed more at Quicken or QuickBooks desktop
instead of QuickBooks Online.
As it turns out, my minimal script seems to work very well with this one weird
anomaly. The nature of it
So, the year isn’t the sticking point. If you look at the .xls files — one
transaction from 2022 and one from 2023 — do you see a difference? If you move
a 2023 transaction to 2022, does it import correctly, or fail? I’m guessing
there’s a column missing in the 2022 xls file.
--
Dave Reiser
This may be slightly off topic, or too late to help, but...
In github, there is a repository
https://github.com/tim-rohrer/move2gnucash
That seems pretty well setup to migrate your data from a quicken csv
export to GC. I haven't used it, but I looked at it for a friend and it
looked
Tom:
On 2023-07-02 15:10, Tom Olin via gnucash-user wrote:
I’m attempting to import data from QuickBooks Online to GnuCash. I’ve written
an awk script which appears to work well except for one major issue.
What format is the data which you export from Quickbooks Online? CSV
(Comma Separated
I’m attempting to import data from QuickBooks Online to GnuCash. I’ve written
an awk script which appears to work well except for one major issue.
The data I’m importing spans the years 2022 and 2023. All 2023 transactions
import cleanly, but all 2022 transactions import unbalanced, meaning I
23 matches
Mail list logo
