Skip to main content
R
rdancey
October 9, 2024
Question

Advanced Reporting Transactions.Classified Account Type Assest

  • October 9, 2024
  • 1 reply
  • 0 views

I am posting this in the hopes that anyone who follows me down this rathole will find it and not spend hours banging their heads against their desks in frustration.

If you are using Advanced Reporting for Quickbooks, which is derived from Qlik, you may discover that a critical constant value inside Quickbooks has a typo.

One of the constants for the Transactions.Classified Account Type field is "Assest", not "Assets"; attempts to extract the desired data from the database will fail unless you have used the correct (typo) constant.


Resolution

When accessing this field, use the constant value "Assest" not "Assets".

Cause

To the best of my ability to determine this is an error inside the QB system and is not actually a Qlix defect.

 

Related Content

I discovered this while using the Advanced Reporting tool in Quickbooks Desktop Enterprise, while modifying one of the default reports provided. Specifically, while working on a report to extract sales data, I found this boilerplate code:

sum(if(Not IsNULL([Item.Item Type]) and Not IsNull([Item.Full Name]) and Not IsNull([Transactions.Txn Type]), if(not Match([Transactions.Classified Account Type], 'Assest','Expense'),[Transactions.Quantity], 0)))

I thought that "Assest" was a typo in the example code and fixed it, which broke this function. Restoring the typo restored the functionality. Thus I deduce this constant is actually embedded into the Quickbooks database and needs to be referenced as is.


Environment

  • Advanced Reporting tool for Quickbooks Desktop Enterprise

1 reply

JenoP
JenoP
October 9, 2024

We truly appreciate your effort in identifying the typo in one of the fields in the Advanced Reporting tool for QuickBooks Desktop Enterprise, rdancey. We take all reported issues seriously, and yours is no exception.

 

Your input is invaluable to us and will contribute significantly to improving our software's performance and reliability. We have already noted this issue and will promptly forward it to our product development team for thorough investigation and resolution.


For immediate assistance with this feature, please don't hesitate to contact our Enterprise Solutions Support team. You can find their contact details here: https://qbar.intuit.com/contact.html


Additionally, you may find the following resources helpful when using this feature:

 

 

Your feedback plays a vital role in helping us enhance our software and improve user experience. The Community is always here to support you, so please don't hesitate to reach out if you need anything else. Once again, thank you for your contribution to making QuickBooks better for everyone.

R
rdanceyAuthor
October 11, 2024

I don't know if you will be able to do anything with this response but this is not a typo in Advanced Reporting. In fact, it appears that the Advanced Reporting team has actually saved your bacon by figuring out that there's a typo inside the Quickbooks Enterprise database itself.

This mistake is not an error in the script. It's an error with the literal constant value for the types of account held in the QB database in the field Transactions.Classified Account Type. That field can hold one of several fixed values and one of them is "Assest" instead of "Assets".

I understand why this has not been fixed as it would likely break all sorts of scripts and internal code and I have no suggestions for you on how it could be fixed.

Terms & ConditionsAccessibility statement