Customize BIS entity class
Concept
In Connectivity studio, if records are imported or exported, each record is wrapped in a BisEntity class. The BisEntitiy class contains all standard methods of the applicable table. The BisEntity class is like a data source on a form.
Standard BIS entity classes
For Connectivity studio, several predefined classes are available that extend the BisEntity class. You can find and view these classes in Microsoft Visual Studio. To do so, go to the BisEntity class and view its hierarchy
Customize BIS entity classes
You can extend the BisEntity class for a table to create a customized BIS entity class. The name of the customized BIS entity class must be Bis[tablename]. You can extend the BisEntity class, for example, to include business logic from the user interface, or to change the standard table methods.
If no customized BIS entity class exists for a table, the standard BisEntity class is used as the wrapper class for records.
If no customized BIS entity class exists for a table, the standard BisEntity class is used as the wrapper class for records.
Example
Item templates in the PLM integration
This example shows how you can overwrite a method. In this case, the BisMessageRunDirect entity class is extended. The new entity class is called BisItemTemplate.
The PLM system distinguishes between production items and buyer items. When a production item is imported and it does not exist, it is created based on a template item called "BomItem". This template item defines the default values for a production item in D365 FO. To apply the right item template, change the onInitEntity method. As a result, based on the template, an item is created with ItemId and RecId empty. These fields are later filled based on the message mapping.