"TypeError" "e.getAttribute is not a function" since 4.12

Question

Hi,

after updating to 4.12, while creating Object-Instances in eniao, we get the following error on ALL development environments.

First the usual:

followed by a new one.

After installing the hotfix the error persisted.
This error seems to have no influence on the functionality.

Does anyone has similar issues?

Thanks,
Robert

Answer 1

Does here a formscript exist?

Comments

Yes, a formscript exists. If needed i can post it it's pretty trivial.

---

This is the CREATE Script.

//Main
scope.model.zpuebelegart.onchange = fillBelegartKurz;


//Functions
function fillBelegartKurz() {
    var belegartKurz = '';
   
    if (scope.model.zpuebelegart.value == 'Rechnung'){
        belegartKurz = 'RECH';
    } else if (scope.model.zpuebelegart.value == 'Gutschrift'){
        belegartKurz = 'GUT';
    } else if (scope.model.zpuebelegart.value == 'Auskunftsanforderung'){
        belegartKurz = 'AA';
    } else if (scope.model.zpuebelegart.value == 'Fakturierbare Auskunft'){
        belegartKurz = 'FAUS';
    } else if (scope.model.zpuebelegart.value == 'Händlerauskunft'){
        belegartKurz = 'HAUS';
    } else if (scope.model.zpuebelegart.value == 'Posteingang'){
        belegartKurz = 'PE';
    } else if (scope.model.zpuebelegart.value == 'Postausgang'){
        belegartKurz = 'PA';
    } else if (scope.model.zpuebelegart.value == 'Telefonnotiz'){
        belegartKurz = 'TNO';
    } else if (scope.model.zpuebelegart.value == 'Gesamtvertragsunterlagen'){
        belegartKurz = 'GSTVU';
    } else if (scope.model.zpuebelegart.value == 'Rechercheunterlagen'){
        belegartKurz = 'RU';
    } else if (scope.model.zpuebelegart.value == 'Verjährungs-Verlängerungs-Vereinbarung'){
        belegartKurz = 'VVV';
    } else if (scope.model.zpuebelegart.value == 'Crefo'){
        belegartKurz = 'CR';
    } else if (scope.model.zpuebelegart.value == 'Besondere Information'){
        belegartKurz = 'BI';
    } else if (scope.model.zpuebelegart.value == 'Sonstiges'){
        belegartKurz = 'SO';
    } else if (scope.model.zpuebelegart.value == 'Mahnung'){
        belegartKurz = 'MAH';
    } else if (scope.model.zpuebelegart.value == 'Rückscheine'){
        belegartKurz = 'RUECKSCH';
    } else if (scope.model.zpuebelegart.value == 'Anwaltsschreiben'){
        belegartKurz = 'ANWSCHR';
    } else if (scope.model.zpuebelegart.value == 'Rückerstattungsstorno'){
        belegartKurz = 'RUECKEST';
    } else if (scope.model.zpuebelegart.value == 'Rückerstattung'){
        belegartKurz = 'RUECKE';
    } else if (scope.model.zpuebelegart.value == 'PC-Gesamtvertrag'){
        belegartKurz = 'PCGSVT';
    }
   
    scope.model.zpuebelegartkurz.value = belegartKurz;
}

Answer 2

Comments

OK, we do not see where this problem notice is coming up. Please can you explane step by step, what you are doing until this notification is coming up?

---

See the other comment please

Answer 3

I am working on the new object

I am changing the field

I am clicking somewhere here

I am accepting the alert

I get an error

Comments

Ok, is fixed within version that has been released on 28th January 2019