Migration 3.3.11 to 4.0.11 - ITSMConfigItem error - RESOLVED

[kruegerM]

@ OTRS 4.0.11
Migrated from OTRS 3.3.8 to 4.0.11 - ran into an issue this morning. -- We have eleven ITSM ConfigItem Classes - when we try to list the configuration items under one of classes using CMDB>Overview, we get the following error:

Kernel::System::ITSMConfigItem::XML::Type:: could not be loaded: Can't locate Kernel/System/ITSMConfigItem/XML/Type/.pm in @INC (@INC contains: /usr/Custom /usr/Kernel/cpan-lib /usr /opt/otrs/Custom /opt/otrs/Kernel/cpan-lib /opt/otrs/ /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 . /etc/httpd) at /opt/otrs//Kernel/System/ObjectManager.pm line 192.

Looking at the ObjectManager.pm file we find:

sub _ObjectBuild {
my ( $Self, %Param ) = @_;

my $Package = $Param{Package};
my $FileName = $Package;
$FileName =~ s{::}{/}g;
$FileName .= '.pm';
eval {
require $FileName;
};

Not sure what should be happening here. And it's only one one of the ITSMConfigItem Classes - all others list fine.

[kruegerM]

Looking at /opt/otrs/Kernel/System/ITSMConfigItem/XML/Type I find:

CustomerCompany.pm
Customer.pm
Date.pm
DateTime.pm
Dummy.pm
GeneralCatalog.pm
Integer.pm
TextArea.pm
Text.pm

all owned by the correct owner/group

rebuilding the ITSMConfigItem package did not change anything.
reinstalling ITSM did not change anything

[kruegerM]

Found the issue.
The Config Items that did not list correctly had a required 'TextArea' field. It did not display as required, and did not require any input when creating a record - however, once a record was created without the field having data - the lists for that item quit displaying.

I copied the definition for the Config Item and removed the 'Required' attribute for the TextArea
Fortunately, I had a copy of the 3.3 system and was able to export a copy of the items.
I then imported them into the 4.0 system under the corrected definition.

Items are now displaying and listing correctly. Not sure if this constitutes a bug, I haven't had the chance to research whether the Admin or Developer manuals warn against requiring TextArea fields. I do know that even if required, you can enter items without the field having data, and in 4.0 - this causes a problem.