When building customizations in Acumatica, it’s common to need a summary value—like the total invoiced goods for a customer during the current year. While it may sound straightforward, using Business Query Language (BQL) to retrieve and aggregate data requires careful handling. One common pitfall...
Working with NULL values in database queries often introduces unexpected behavior, especially when using frameworks that abstract SQL logic like Acumatica's BQL Fluent syntax. One common scenario is attempting to retrieve records based on a nullable key field, such as SubItemID in the POVendorInv...
When customizing Acumatica screens, for example like printing invoices, there are subtle pitfalls that you need to be aware of. In our extended ARPrintInvoices screen, we encountered two major challenges:
Extending Original Logic Requires a Complete Copy of GetBQLStatement
Retrieving Complete Cu...
If you want to create custom Attribute for autonumbering field you need:
Create Setup page for configuring autonumbering field or maybe you can use existing
Create Attribute which you'll add to your entity
Add attribute to field that you need increment
Create Setup page for co...
Hello everybody,
today I want to write a few words about operator in which was presented in SQL for long ago, but weren't available in Acumatica BQL. But time goes on and now you can use it. For example like this:
Object[] values = new String[] { "BXW000004", "B...