nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

User Business Class - How to include IDM.BusinessClass code

Vikram Reddy

Hi,

I created a User Business Class (a copy of the delivered HSReportDocument300) that generates a file based on an IDM template. However, I'm receiving a syntax error when I reference IDM.XXXHSReportDocument300 within the User Business Class.

Is it possible to include or reference the delivered IDM business class code from a User Business Class? If not, what is the recommended alternative approach to achieve the same functionality while leveraging the IDM template and related business logic?

Find more posts tagged with

LPL

Landmark

Comments

Vikram Reddy

@Andrew Lipetzky I would appreciate your thoughts and recommendations on this.

Michael Cleverly

Hi Vikram,

In the SpecRepository there is both a HSReportDocument300.busclass and a HSReportDocument300.IDM.busclass file.

Since User Business Classses don't currently support the (what I'll call rule block separation, though I have no idea what the Landmark team calls it internally) rule block form of BusinessClass.RuleBlock.busclass, if you want a UBC that recreates the delivered one you'd need to inline and interleave the portions from HSReportDocument300.IDM.busclassinto your UBC to synthesize it as a single business class (which is what Landmark must effectively do at runtime for the delivered ones).

Dr_Awesome

So they are called Business Class Extensions.

Naming convention:<BusinessClassName>.<ExtensionFeature>.busclass

They are modular LPL specification files used to extend a core business class with domain-specific, subsystem, or integration-level capabilities without modifying or bloating the base .busclass definition.

And yep, the base .busclass and all corresponding .<ExtensionFeature>.busclass extensions are composed into a unified business object model in memory.

Yeah, since you cannot configure your own extension, or match a delivered one to a UBC, you'll need to inline what you need into your UBC, as Michael said.

Oh, I'm assuming you weren't talking about the more basic usage of "include IDM.<something>" in your UBC? That may have it's own trouble in a UBC that you need to inline as well. Referencing a central rule block definition is something that has been discussed opening up in configuration console.

Copyright © 2026 Infor. All rights reserved.