# Cdata error when querying Quickbooks JournalEntryLineItems

**URL:** <https://community.cdata.com/t/cdata-error-when-querying-quickbooks-journalentrylineitems/1326>\
**Category:** CData Connect AI\
**Tags:** question, quikbooks, cdata-error, journalentrylineitems, quickbooks, cdata, journalentry\
**Created:** [September 3, 2026, 4:01pm UTC](https://community.cdata.com/t/cdata-error-when-querying-quickbooks-journalentrylineitems/1326 "2026-09-03T16:01:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lesh](https://avatars.discourse-cdn.com/v4/letter/l/6f9a4e/32.png) [@lesh](https://community.cdata.com/u/lesh)\
**Post date:** [September 3, 2026, 4:01pm UTC](https://community.cdata.com/t/cdata-error-when-querying-quickbooks-journalentrylineitems/1326/1 "2026-09-03T16:01:57Z")

</div>

I am encountering this error since yesterday, JournalEntries seems OK but the JournalEntryLineItems returns this error.

 ![d5660baa-79c0-44ec-87b3-ca2f2d1b9c24.png](https://us1.discourse-cdn.com/cdata/original/1X/21794f611b97c8a322c68a0ce9e64b6283ca8bb9.png)

---

<div class="post-metadata">

**Author:** ![Ethem\_Q](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/ethem_q/32/1997_2.png) [@Ethem\_Q](https://community.cdata.com/u/Ethem_Q)\
**Post date:** [September 3, 2026, 6:09pm UTC](https://community.cdata.com/t/cdata-error-when-querying-quickbooks-journalentrylineitems/1326/2 "2026-09-03T18:09:54Z")

</div>

Hi&nbsp; ​ @lesh &nbsp;Based on the error message it looks like the issue is with the LineNum column being sent as **[Line.LineNum]** in the query projection for you instead of&nbsp;**[Line\_LineNum]**

 ![ae8cbce9-4249-4fdd-9c26-2fe5d9b11c67.png](https://us1.discourse-cdn.com/cdata/original/1X/7855abc4c4e49e6ab98377b90101233046ded00a.png)

Can you double check on your end if the column in question is exposed as Line\_LineNum in the column metadata? Also can you confirm the issue happens only when running a SELECT \* query? What happens if you try running the following query as a workaround?

```auto
SELECT [LineId], [JournalEntryId], [SyncToken], [MetaData_CreateTime], [MetaData_LastUpdatedTime], [DocNumber], [TxnDate], [PrivateNote], [Adjustment], [Line_Id], [Line_Description], [Line_Amount], [Line_DetailType], [Line_LineNum], [Line_JournalEntryLineDetail_PostingType], [Line_JournalEntryLineDetail_Entity_Type], [Line_JournalEntryLineDetail_Entity_EntityRef], [Line_JournalEntryLineDetail_Entity_EntityRef_Name], [Line_JournalEntryLineDetail_AccountRef], [Line_JournalEntryLineDetail_AccountRef_Name], [Line_JournalEntryLineDetail_ClassRef], [Line_JournalEntryLineDetail_ClassRef_Name], [Line_JournalEntryLineDetail_DepartmentRef], [Line_JournalEntryLineDetail_DepartmentRef_Name], [Line_JournalEntryLineDetail_TaxCodeRef], [Line_JournalEntryLineDetail_TaxApplicableOn], [Line_JournalEntryLineDetail_TaxAmount], [Line_JournalEntryLineDetail_BillableStatus], [Line_JournalEntryLineDetail_TaxInclusiveAmt], [TxnTaxDetail_TxnTaxCodeRef], [TxnTaxDetail_TotalTax], [TxnTaxDetail_TaxLineAggregate], [TotalAmt], [CurrencyRef], [CurrencyRef_Name], [ExchangeRate], [ProjectRef] FROM [QuickBooksOnline1].[QuickBooksOnline].[JournalEntryLineItems]

```

As for the issue, if the problem is reproduced&nbsp;from a simple SELECT \* FROM JournalEntryLineItems query then we would need to take a look at the log to better understand why the underlying query is sending this column as Line.LineNum. Please submit a support case with the CData support team [here](https://portal.cdata.com/?a=support)&nbsp;and send the logs over so one of our support specialists will further assist you.

---

<div class="post-metadata">

**Author:** ![lesh](https://avatars.discourse-cdn.com/v4/letter/l/6f9a4e/32.png) [@lesh](https://community.cdata.com/u/lesh)\
**Post date:** [September 3, 2026, 6:41pm UTC](https://community.cdata.com/t/cdata-error-when-querying-quickbooks-journalentrylineitems/1326/3 "2026-09-03T18:41:11Z")

</div>

> [@Ethem\_Q](#):
>
> Hi&nbsp; ​ @lesh &nbsp;Based on the error message it looks like the issue is with the LineNum column being sent as **[Line.LineNum]** in the query projection for you instead of&nbsp;**[Line\_LineNum]**
> 
> ![ae8cbce9-4249-4fdd-9c26-2fe5d9b11c67.png](https://us1.discourse-cdn.com/cdata/original/1X/7855abc4c4e49e6ab98377b90101233046ded00a.png)
> 
> Can you double check on your end if the column in question is exposed as Line\_LineNum in the column metadata? Also can you confirm the issue happens only when running a SELECT \* query? What happens if you try running the following query as a workaround?
> 
> ```auto
> SELECT [LineId], [JournalEntryId], [SyncToken], [MetaData_CreateTime], [MetaData_LastUpdatedTime], [DocNumber], [TxnDate], [PrivateNote], [Adjustment], [Line_Id], [Line_Description], [Line_Amount], [Line_DetailType], [Line_LineNum], [Line_JournalEntryLineDetail_PostingType], [Line_JournalEntryLineDetail_Entity_Type], [Line_JournalEntryLineDetail_Entity_EntityRef], [Line_JournalEntryLineDetail_Entity_EntityRef_Name], [Line_JournalEntryLineDetail_AccountRef], [Line_JournalEntryLineDetail_AccountRef_Name], [Line_JournalEntryLineDetail_ClassRef], [Line_JournalEntryLineDetail_ClassRef_Name], [Line_JournalEntryLineDetail_DepartmentRef], [Line_JournalEntryLineDetail_DepartmentRef_Name], [Line_JournalEntryLineDetail_TaxCodeRef], [Line_JournalEntryLineDetail_TaxApplicableOn], [Line_JournalEntryLineDetail_TaxAmount], [Line_JournalEntryLineDetail_BillableStatus], [Line_JournalEntryLineDetail_TaxInclusiveAmt], [TxnTaxDetail_TxnTaxCodeRef], [TxnTaxDetail_TotalTax], [TxnTaxDetail_TaxLineAggregate], [TotalAmt], [CurrencyRef], [CurrencyRef_Name], [ExchangeRate], [ProjectRef] FROM [QuickBooksOnline1].[QuickBooksOnline].[JournalEntryLineItems]
> 
> ```
> 
> As for the issue, if the problem is reproduced&nbsp;from a simple SELECT \* FROM JournalEntryLineItems query then we would need to take a look at the log to better understand why the underlying query is sending this column as Line.LineNum. Please submit a support case with the CData support team [here](https://portal.cdata.com/?a=support)&nbsp;and send the logs over so one of our support specialists will further assist you.

Hi Yes, it is exposed as Line\_LineNum on my end.

I’ll file a case with the support team.

 ![d9d2a2ad-6426-4d11-bad7-6bb1607a5844.png](https://us1.discourse-cdn.com/cdata/original/1X/05fd6d507ffcbaf53b94e101beee725733bad685.png)
