invoicer | Invoicer helps you generate invoice documents | Business library

Instead of using external class like this

The solution is simple. You need to add a schemaVersion property to your root class and annotate it with @XmlAttribute, not with @XmlElement.

I would set cancel_date as database field when you set cancel flag. Then you can use single query:

I would suggest to make use of the acumatica customization project feature. This is accessible from the customization project. For this approach you have two possible scenarios. If a button is only required to show a report only and no additional logic. In this case you can just specify the button in the actions section of the screen in the customization project as seen in the below screenshot.

The other option is to define the button in the code and then also go to the actions section of the customization project and instead of add new you can select add existing. This will add your existing button and you'll be able to specify that you want it to be under the reports menu.

First of all, repository is just a thin layer on top of EM (an extension point if you want), that bares the entity name so you don't have to pass it to the first parameter of EM method (e.g. em.find(Ent, ...) vs repo.find(...).

Then the contexts - you need a dedicated context for each request, so it has its own identity map. If you use RequestContext helper, the context is created and saved via domain API. Thanks to this, all the methods that are executed inside the domain handler will use the right instance automatically - this happens in the em.getContext() method, that first checks the RequestContext helper.

https://mikro-orm.io/docs/identity-map/#requestcontext-helper-for-di-containers

Check the tests for better understanding of how it works:

https://github.com/mikro-orm/mikro-orm/blob/master/tests/RequestContext.test.ts

So if you use repositories, with RequestContext helper it will work just fine as the singleton repository instance will use the singleton EM instance that will then use the right request based instance via em.getContext() where approapriate.

But if you use manual forking instead, you are responsible use the right repository instance - each EM fork will have its own one. So in this case you can't use a singleton, you need to do forkedEm.getRepository(Ent).

Btw alternatively you can also use AsyncLocalStorage which is faster (and not deprecated), if you are on node 12+. The RequestContext helper implementation will use ALS in v5, as node 12+ will be requried.

https://mikro-orm.io/docs/async-local-storage

Another thing you could do is to use the RequestContext helper manually instead of via middlewares - something like the following:

Pass BuildContext to your function like

Use a subquery:

This is not possible with standard functionality.

Netsuite have a SuiteSolution for Consolidated Invoicing.. You should speak with your NetSuite/Partner Account Manager

To use aggregate functions like SUM, AVG, COUNT etc, you need to specify GROUP BY condition. Like this: