Forum GLPI-Project

clrudolphi

Member

Registered: 2025-03-05

Posts: 2

Rules supported with Inventory DataInjector Plugin?

Are Business Rules enforced when importing Inventory via DataInjector?
(using v10.0.17) with the Data Injector plugin

Experimenting with using the Data Injector. My organization would like to enforce that certain fields are mandatory on imports of Computers via CSV (such as Name, Location, Status, Type, Manufacturer, and Model).

I have attempted this by creating rules within "Rules for import and link equipments" but without any luck. The rules are 'active' and near the top of the Computers section.

Does the Data Injection plug-in support enforcement of these Business Rules (or are they bypassed or only for native Inventory)?

Should this be accomplished some other way?

TIA

cconard96

Moderator

Registered: 2018-07-31

Posts: 3,263

Website

Re: Rules supported with Inventory DataInjector Plugin?

It would be similar to as if you manually created/updated those assets. Rules for import and link equipments work for assets imported through the automatic inventory process only. Business Rules for Assets should still run though.

---

GLPI Collaborator and Plugin Developer.
My non-English comments are automated translations. Sorry for any confusion that causes.
Mes commentaires non anglais sont des traductions automatiques. Désolé pour toute confusion qui cause.
Mis comentarios que no están en inglés son traducciones automáticas. Perdón por cualquier confusión que cause.

clrudolphi

Member

Registered: 2025-03-05

Posts: 2

Re: Rules supported with Inventory DataInjector Plugin?

@cconard96 - Thank you for the information.
What action(s) is possible within the 'Business Rules for Assets'? I have attempted to create Rules in that section but have struggled to understand how to use it properly to attain my objective.
For example, when creating a rule on Status, I can test for Status in the Constraint section, but none of the available Actions make much sense to me. What do most implementations use when attempting to vet Asset records and identify those that are incomplete or malformed? Ideally, we would like to reject the import (from the DataInjector) - but that seems not possible. Barring that, what do other users do? Does it make sense to define an 'unknown' value for those fields that are not within the allowed range of values; or simply leave them blank? Is it possible to tag the record somewhere else with a flag indicating that follow-up is required to clean up the record?

What can be done about fields that cannot be examined within the 'Rules for Assets' section? For example, I cannot find a way to create a criteria on the Computer Types field.