Uploaded image for project: 'Project Configurator Plugin'
  1. PCP-734

"Used by" report: if a null custom field is found while analyzing custom field values for exported projects, an exception prevents correct error reporting


    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.2.0-J6, 2.2.0-J7
    • Fix Version/s: 2.2.1-J6, 2.2.1-J7
    • Security Level: Public (Issues everybody can see)


      The user sees a generic entity error which does not give a clue about the real origin of the problem. This is the error:

      ProjectConfigSerializingContext]  [GenericEntity.get] "name" is not a field of CustomFieldValue
      java.lang.IllegalArgumentException: [GenericEntity.get] "name" is not a field of CustomFieldValue
                      at org.ofbiz.core.entity.GenericEntity.get(GenericEntity.java:246)
                      at org.ofbiz.core.entity.GenericEntity.getString(GenericEntity.java:462)
                      at com.awnaba.projectconfigurator.projectconfigserialize.ExportManager.countCFValuesPerCF(ExportManager.java:212)

      The null custom field may be caused by two reasons:

      • Its custom field type is defined in a plugin that was disabled (more likely)
      • The custom field was deleted and some custom field values were left behind (quite unlikely)

      The fix covers both cases. In the first one, it will issue a useful message as defined in PCP-384 Resolved . the second one will be ignored, as there is nothing the user can do in that case (maybe except removing the orphaned custom field value).




            • Assignee:
              pepe.maranon José Marañón [Awnaba Software S.L.]
              pepe.maranon José Marañón [Awnaba Software S.L.]
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: